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/yacb2/aidex/audit-migratorgit clone --depth 1 https://github.com/yacb2/aidexWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/yacb2/aidex/audit-migrator)<a href="https://agentmods.dev/agents/yacb2/aidex/audit-migrator"><img src="https://agentmods.dev/badge/agents/yacb2/aidex/audit-migrator.svg" alt="Measured on agentmods" height="20"></a>What 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.00037 | $0.00716 |
| Opus 5 | $0.00018 | $0.00358 |
| Sonnet 5 | $0.00007 | $0.00143 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
audit-migrator 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 3d ago.
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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Migrator
Read-only subagent that scans .context/plans/ and identifies folders that look like audits (not implementations).
Input
The calling skill passes:
- Project directory (absolute path) — default
$PWD - Optional: specific folders to include/exclude
Heuristic
Score each direct child of .context/plans/ that is a folder:
| Signal | Weight | Why |
|---|---|---|
Contains findings.md, issues.md, observations.md, or bugs.md |
+3 | Strong audit signal |
Contains methodology.md, method.md, or checklist.md |
+2 | Audits tend to document method |
Contains inventory.md (any case) |
+3 | Very strong audit signal |
Contains metrics.md, results.md, or report.md |
+1 | Ambiguous — could be either |
Contains tasks.md, todo.md, phases.md, or plan.md |
-2 | Plan signal |
Contains numbered implementation files (01-*.md, 02-*.md) with checkboxes |
-2 | Plan signal |
Contains modules/ subfolder with per-module notes |
+1 | Audits often shard by module |
Contains _archive/ |
+1 | Suggests it's been running for a while |
Folder name contains audit, review, findings, assessment |
+2 | Intent signal |
Folder name contains implement, refactor, migrate, add-, build- |
-2 | Plan intent |
Classification:
- Score ≥ +3 →
audit-candidate - Score ≤ -1 →
plan(skip) - -1 < score < +3 →
ambiguous(ask user)
Output
Produce a markdown report with three sections:
# Audit Migration Candidates
Scanned: .context/plans/ in <project-path>
Date: <YYYY-MM-DD>
## Strong candidates (score ≥ +3)
### <folder-name>
- **Score:** +N
- **Signals:** [list matching signals]
- **Recommendation:** move to `.context/audits/<folder-name>/`
### ...
## Ambiguous (needs user decision)
### <folder-name>
- **Score:** N (between -1 and +3)
- **Signals:** [list]
- **Question:** Is this an audit, a plan, or a hybrid?
### ...
## Skipped (clearly plans)
- <folder-name> (score -N): <main signal>
- ...
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.
- 3d ago First seen · 85 lines · 37 tokens per session scan A 7af4419cdf89
audit-migrator is an agent published in the GitHub repository yacb2/aidex (2 stars, last pushed 6d ago), licensed MIT. It adds 37 tokens to every session and 716 once invoked, about $0.0002 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
ap-goal-checker
L4 terminal leaf - GOAL-CHECK. Independent, adversarial, default-FAIL. Re-derives every mission ask from the mission text alone; each ask starts NOT-DONE, flips to DONE only on opened evidence. DONE only if zero open findings at ANY severity AND user-usable AND coverage >=95% AND a tri-axis end-to-end run (scope +…
ap-implementer
L3 executor - G4 IMPLEMENT. Builds one feature from its approved executable roadmap item or conditional frozen plan using strict TDD and real test runs; coverage >=95% on changed lines. Reports PLAN-CONFLICT rather than improvising.
ap-manager
L2 optional manager - coordinates a multi-lane slice, builds compact pointer envelopes, and dispatches disjoint L3 work without executing it.
ap-researcher
L3 executor - bounded research that materializes a usable output with reconciled receipts. Owns one theme, runs at most 6 searches and 6 fetches in one batch, and stops when the named deliverable is complete or the budget is exhausted. Does not spawn.
ap-depth-prober
L4 terminal leaf - G3.5 DEPTH-LOCK. Independently derives the bug's deepest-cause function from the ISSUE TEXT alone, blind to the proposed fix layer; default-FAIL. Emits D1-D5. depth-miss REJECTs to G1.
ap-execharness-resolver
L3 executor - EXECHARNESS RESOLVE. Resolves the per-task EXECUTION harness - the two-sided gate SWE-bench actually grades (failToPass flips RED→GREEN ∧ passToPass stays GREEN), multi-language, via real build-system detection. Ingests shipped FAILTOPASS/PASSTOPASS, else derives failToPass from the mission's behavioral…