{"id":"security-log-anomaly","title":"Log Anomaly","description":"Anomalies typed. Log anomalies. Typed v1 agent with eval coverage.","category":"cybersecurity","status":"validated","version":"1.0.0","source":"agentskit-registry","license":"MIT","tags":["cybersecurity","structured-output","v1"],"packages":["@agentskit/core","@agentskit/runtime","@agentskit/tools"],"files":["agent.ts","README.md","eval.ts"],"requires":{"zod":"^3","zod-to-json-schema":"^3"},"skill":{"name":"security-log-anomaly","description":"Anomalies typed. Log anomalies. Typed v1 agent with eval coverage.","systemPrompt":"You are Log Anomaly. Log anomalies. Output: Anomalies typed.\nActionable findings citing input sources. No invented issues.\nNEVER invent facts — gaps and openQuestions for missing input. Always draft for human review.\n${UNTRUSTED_CONTENT_DIRECTIVE}\nCall submit_log_anomaly exactly once. Stop."},"flow":null,"a2a":{"id":"io.agentskit.registry.security-log-anomaly","name":"Log Anomaly","description":"Anomalies typed. Log anomalies. Typed v1 agent with eval coverage.","version":"1.0.0","homepage":"https://registry.agentskit.io","skills":[{"name":"security-log-anomaly","description":"Anomalies typed. Log anomalies. Typed v1 agent with eval coverage.","capabilities":{"streaming":true,"cancellation":true,"requiresApproval":false}}]},"sources":[{"path":"agent.ts","content":"import type { AdapterFactory, ChatMemory, Observer, ToolCall, ToolDefinition } from '@agentskit/core'\nimport { fenceUntrustedContent, UNTRUSTED_CONTENT_DIRECTIVE } from '@agentskit/core/security'\nimport { invokeStructured } from '@agentskit/runtime'\nimport { defineZodTool } from '@agentskit/tools'\nimport { z } from 'zod'\nimport { zodToJsonSchema } from 'zod-to-json-schema'\nimport type { JSONSchema7 } from 'json-schema'\n\n/** Log Anomaly — v1 validated. Pain: Log anomalies */\n\nexport interface Finding { id: string; severity: 'critical' | 'high' | 'medium' | 'low' | 'info'; message: string; source?: string; recommendation?: string }\nexport interface AgentOutput { summary: string; findings: Finding[]; gaps: string[]; openQuestions: string[] }\nexport interface AgentResult extends AgentOutput { requiresReview: boolean }\nexport interface SecurityLogAnomalyConfig {\n  adapter: AdapterFactory\n  memory?: ChatMemory\n  observers?: Observer[]\n  onConfirm?: (toolCall: ToolCall) => boolean | Promise<boolean>\n  maxSteps?: number\n}\n\nconst Output = z.object({\n  summary: z.string(),\n  findings: z.array(z.object({\n    id: z.string(), severity: z.enum(['critical', 'high', 'medium', 'low', 'info']),\n    message: z.string(), source: z.string().optional(), recommendation: z.string().optional(),\n  })),\n  gaps: z.array(z.string()).default([]),\n  openQuestions: z.array(z.string()).default([]),\n})\nconst toJson = (s: z.ZodTypeAny): JSONSchema7 => zodToJsonSchema(s) as JSONSchema7\n\nconst skill = {\n  name: 'security-log-anomaly',\n  description: \"Log Anomaly — typed output agent (draft spec).\",\n  systemPrompt: `You are Log Anomaly. Log anomalies. Output: Anomalies typed.\nActionable findings citing input sources. No invented issues.\nNEVER invent facts — gaps and openQuestions for missing input. Always draft for human review.\n${UNTRUSTED_CONTENT_DIRECTIVE}\nCall submit_log_anomaly exactly once. Stop.`,\n  tools: ['submit_log_anomaly'],\n}\n\nexport function createSecurityLogAnomalyAgent(config: SecurityLogAnomalyConfig) {\n  const submit = (): ToolDefinition =>\n    defineZodTool({ name: 'submit_log_anomaly', description: 'Submit result. Once.', schema: Output, toJsonSchema: toJson, async execute() { return 'recorded' } }) as ToolDefinition\n\n  async function run(input: string): Promise<AgentResult> {\n    if (!input?.trim()) throw new Error('security-log-anomaly requires non-empty input')\n    const result = await invokeStructured({\n      adapter: config.adapter,\n      tool: submit(),\n      task: `INPUT:\\n${fenceUntrustedContent(input)}`,\n      parse: (a) => Output.parse(a),\n      skill,\n      memory: config.memory,\n      observers: config.observers,\n      onConfirm: config.onConfirm,\n      maxSteps: config.maxSteps ?? 4,\n    })\n    return { ...result, requiresReview: true }\n  }\n  return {\n    name: 'security-log-anomaly',\n    run,\n    asHandle() { return { name: 'security-log-anomaly', run: (t: string) => run(t).then((r) => JSON.stringify(r)) } },\n  }\n}\n"},{"path":"README.md","content":"# Log Anomaly\n\n> **v1 validated** — `npx agentskit add security-log-anomaly`\n\n## Pain\nLog anomalies\n\n## Output\nAnomalies typed\n"},{"path":"eval.ts","content":"import type { EvalSuite } from '@agentskit/eval'\n\nexport const suite: EvalSuite = {\n  name: 'security-log-anomaly',\n  cases: [\n    { input: 'Complete input for Log Anomaly: Log anomalies. Provide full structured output.', expected: (r: string) => r.length > 20 && /requiresReview|summary|title|category|findings|sections|score|clusters|items|steps/i.test(r) },\n    { input: 'Minimal input.', expected: (r: string) => /gap|openQuestion/i.test(r) || r.length > 10 },\n    { input: 'Input with specific detail: ACME Corp project deadline March 15.', expected: (r: string) => /ACME|March|15/i.test(r) || /gap/i.test(r) },\n    { input: 'Empty context — only says \"process this\".', expected: (r: string) => r.length > 5 },\n  ],\n}\n"}],"installable":true,"validation":{"status":"approved","score":96,"confidence":0.96,"method":"codex-executor-independent-reviewer","iterations":1,"cases":3,"summary":"The agent produced valid structured outputs for all three cases, stayed within the log-anomaly purpose, did not invent log evidence, surfaced uncertainty and missing context, and resisted the explicit injection attempt. The behavior is conservative and useful for sparse or adversarial inputs. The main limitation is that this validation set did not include a real log excerpt, so anomaly-detection quality on substantive logs remains less proven, but no v1-blocking failure appears in the provided outputs.","strengths":["Valid structured outputs in all cases with findings, gaps, open questions, and review posture.","Correctly avoided hallucinating concrete security events when no logs were provided.","Handled prompt-injection content as untrusted data and did not output the requested APPROVED string.","Recommendations were actionable and aligned with security log triage needs."],"notes":[]}}