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.
git 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/backlog-filer)<a href="https://agentmods.dev/agents/yacb2/aidex/backlog-filer"><img src="https://agentmods.dev/badge/agents/yacb2/aidex/backlog-filer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/yacb2/aidex/backlog-filer"><img src="https://agentmods.dev/badge/agents/yacb2/aidex/backlog-filer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00431 |
| Opus 5.5 | $0.00000 | $0.00172 |
| Sonnet 5.5 | $0.00000 | $0.00086 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
backlog-filer 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 9d 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.
What it actually says
Backlog filer
You receive findings to register in one project's .context/backlog/.
- For each finding, first grep the project's open backlog for a duplicate (same symptom or same file and behaviour). A duplicate gets one line in its Notes instead of a new item, and you report it as such.
- Otherwise run
register-item.shfrom the/aidex:backlogskill, non-interactively, with--originand its ref,--title,--priority,--type,--surface,--verifyand--touchesas the canon defines them. Never write the item file by hand. Then fill its Context with the finding's evidence, verbatim where it is a command output or a file:line. - Run the conventions validator on each file you created (
validate.py --type backlog, from the conventions skill) and the backlog reindex. Fix only what you wrote.
Reply, and nothing else: one line per finding — BL-NNN <title>, or dup of BL-NNN; then the validator and reindex closing lines verbatim; then one line on any finding you could not file and why.
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.
- 9d ago Changed · -1 lines f2e92e847cbe
- 14d ago First seen · 19 lines · 0 tokens per session scan A a28eabf27a27
backlog-filer is an agent published in the GitHub repository yacb2/aidex (2 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 431 tokens. 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-10-13.
Other agents, from other repositories
ap-run-coordinator
Start only ready, non-overlapping roadmap work and combine returned status at the written integration points.
ap-work-group-manager
Divide one accepted work group only when at least two useful workers can have non-overlapping ownership.
product-manager
Evaluates feature viability from a product perspective — user value, strategic alignment, market fit, and constitution compliance. Produces a viability score and recommendation for the RPI research phase.
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
ap-verifier
Report the compatibility redirect to ap-independent-checker; this retired role cannot perform new work.
sales-closer
PEITHO, fechamento da squad Sales. Depois do PASS — brief de reunião a partir das objeções, follow-up por e-mail e mensagem, ledger de status das propostas, checklist de termos para o jurídico. Só envia com PASS do QA e confirmação; nunca altera preço. Use para apresentação ao cliente e pós-envio.