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 commands/uditgoenka/autoresearch/securitygit clone --depth 1 https://github.com/uditgoenka/autoresearchWhat 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.00018 | $0.01263 |
| Opus 5 | $0.00009 | $0.00632 |
| Sonnet 5 | $0.00004 | $0.00253 |
| Haiku 4.5 | $0.00002 | $0.00126 |
Grade A, and why
autoresearch:security 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- autoresearch_security — 95% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EXECUTE IMMEDIATELY.
Parse Arguments
Extract from $ARGUMENTS:
Scope:or--scope— file globs to auditFocus:— specific area (auth, API, data handling, etc.)Depth:or--depth— quick (5 iterations), standard (15), deep (30+)Iterations:or--iterations— default 15. "unlimited" for unbounded.--diff— delta mode: only audit files changed since last audit--fix— after audit, auto-fix Critical/High findings (chains to fix)--fail-on <severity>— exit non-zero if findings at/above threshold (CI gate)--evals,--evals-interval N,--chain,--<subcommand>
Setup (if required context missing)
If Scope missing and no --diff:
- Scan codebase for tech stack, frameworks, API routes
- AskUserQuestion (single batch): Q1 (Scope): "What to audit?" — entire codebase, API + middleware, auth, external-facing Q2 (Depth): "How thorough?" — quick (5), standard (15), deep (30+), unlimited Q3 (Action): "What to do with findings?" — report only, report + auto-fix, report + CI gate If all provided → skip.
Setup Phase (once, before loop)
- Reconnaissance — scan: package.json/requirements.txt (deps), .env.example (secrets), Dockerfile (infra), API route files (attack surface), auth/middleware (trust boundaries), DB schemas (data assets), CI/CD configs (supply chain)
- Asset Identification — catalog data stores, auth systems, external services, user inputs
- Trust Boundary Mapping — browser↔server, public↔authenticated, user↔admin, CI↔prod
- STRIDE Threat Model — generate threats per category. Load
references/security-checklist.mdfor checklist. - Attack Surface Map — entry points, data flows, abuse paths
- Baseline — count known issues, initialize coverage tracking
Create output directory: autoresearch/security-{YYMMDD}-{HHMM}/
Write: overview.md, threat-model.md, attack-surface-map.md
TSV header: # metric_direction: higher_is_better\niteration\ttimestamp\tfinding\tseverity\towasp\tstride\tevidence\tfile_line
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 · 102 lines · 18 tokens per session scan A 3a8aba600475
autoresearch:security is a command published in the GitHub repository uditgoenka/autoresearch (5,966 stars, last pushed 19d ago), licensed MIT. It adds 18 tokens to every session and 1,263 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-30.
Other commands, from other repositories
drift
Read the Genesis build phases document: docs/architecture/genesis-v3-build-phases.md.
challenge
Read the specified design doc section.
thoth:dashboard
Alias for status --dashboard; manage the local dashboard backed by .thoth ledgers.
thoth:doctor
Alias for status --doctor; strictly audit project health without writing authority.
feature
End-to-end feature/bug-sweep workflow for aitm — understand, reproduce against a real run, explore and build with a hive of parallel agents in this one checkout (never worktrees), path-disjoint slices, verify under Bun AND Node, PR, merge, and (only when asked) release to npm. Tracks in GitHub issues. Reads intent…
merge-pr
Drive an open PR to merge, then advance to the next PR group.