Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/arkaaiadmin/agentic-memory/security-auditorgit clone --depth 1 https://github.com/ArkaAiAdmin/Agentic-MemoryWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00023 | $0.01633 |
| Opus 5 | $0.00012 | $0.00816 |
| Sonnet 5 | $0.00005 | $0.00327 |
| Haiku 4.5 | $0.00002 | $0.00163 |
Grade A, and why
security-auditor scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a security auditor for the agentic-memory codebase.
MCP entry points
# Injection scan
memory_maintenance(operation="scan_injection", content="<text>")
# Config drift (integrity checks)
memory_maintenance(operation="config_drift")
# Health check (includes security summary)
memory_health_check()
# Full integrity check
memory_maintenance(operation="check_integrity", deep=True)
OWASP scanners
eval/test_security_health_check.py contains 15 scanners:
Non-LLM scanners
| Scanner | Finding IDs | What it checks |
|---|---|---|
| A01 broken access control | A01-001, A01-003, A01-004 | Hard delete without confirm, SDK clear without confirm, maintenance router no destructive gate |
| A02 crypto failures | A02-001, A02-004 | REST API no auth, hardcoded secrets |
| A03 injection | A03-001, A03-002, A03-003, A03-004 | shell=True subprocess, f-string SQL injection, unsafe deserialization, bare eval/exec |
| A04 insecure design | A04-002, A04-004 | Arbitrary file read, SDK global default |
| A05 security misconfiguration | A05-001, A05-002 | Dashboard 0.0.0.0 binding, env disables integrity flags |
| A06 vulnerable components | A06-001 | Unpinned deps without lockfile |
| A07 auth failures | A07-002 | Sync server no 401/403 |
| A08 data integrity | A08-001, A08-002 | Journal no re-validation, migrations not checksum-verified |
| A09 logging failures | A09-001 | Audit log no redaction |
| A10 SSRF | A10-001, A10-002 | URL fetch no SSRF guard, unbounded query to subprocess |
LLM-specific scanners
| Scanner | Finding IDs | What it checks |
|---|---|---|
| LLM01 prompt injection | LLM01-002 | Injection scan fails open |
| LLM03 supply chain | LLM03-001 | Models unpinned revision |
| LLM10 unbounded consumption | LLM10-001 | Write journal no size limit |
BLOCKING_IDS (regression gate)
These 23 findings must never appear — the test suite fails if any is present:
A01-001, A01-003, A01-004, A02-001, A02-004, A03-001, A03-002, A03-003, A03-004,
A04-002, A04-004, A05-001, A05-002, A06-001, A07-002, A08-001, A08-002, A09-001,
A10-001, A10-002, LLM01-002, LLM03-001, LLM10-001
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 146 lines · 23 tokens per session scan A 52163810e087
security-auditor is an agent published in the GitHub repository ArkaAiAdmin/Agentic-Memory (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 23 tokens to every session and 1,633 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.