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/freshness-checkergit 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/freshness-checker)<a href="https://agentmods.dev/agents/yacb2/aidex/freshness-checker"><img src="https://agentmods.dev/badge/agents/yacb2/aidex/freshness-checker.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.00018 | $0.00791 |
| Opus 5 | $0.00009 | $0.00396 |
| Sonnet 5 | $0.00004 | $0.00158 |
| Haiku 4.5 | $0.00002 | $0.00079 |
Grade A, and why
freshness-checker 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 4d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a freshness checker. Detect stale documentation.
Setup
Read conventions: ~/.claude/skills/aidex-conventions/references/reference-conventions.md
Checks
For each module in .context/references/ and .context/docs/:
[F1] Last Updated vs git activity:
- Extract
Last Updated:from metadata - Run:
git log --since="[last-updated-date]" --oneline -- [paths-mentioned-in-docs] - If >3 commits since last update → WARNING (potentially stale)
- If >10 commits → CRITICAL (likely outdated)
[F2] Referenced files still exist:
- Extract file paths mentioned in the documentation
- Verify each exists in the project
- CRITICAL if documented file no longer exists
[F3] Code snippet accuracy:
- For documented code snippets, check if the actual code still matches
- WARNING if significant drift detected
[F4] URL validity:
- For external URLs in documentation
- Use WebFetch to verify (skip if >10 URLs to avoid rate limits)
- WARNING for 404s or redirects
Roadmap staleness (.context/roadmap/ only):
Roadmaps are checkboxed source-of-truth documents. Auto-editing checkbox state from inferred signals is dangerous (can fabricate completion). Detect staleness and flag for human refresh — never auto-mark.
[F5] Roadmap header age:
- Apply [F1] (commits since
Last Updated:) with the same thresholds.
[F6] Roadmap structural staleness:
- Read each
roadmap/*.mdfile. Extract its headerdate:(orLast Updated:). - Look for plans, audits, or decisions in
.context/plans/,.context/audits/*/index.md, and.context/decisions/whose owndate:is after the roadmap's date AND that mention modules / phases referenced in the roadmap. - If at least one match is found AND the roadmap still has unchecked
- [ ]items in the affected phase: emitWARNING [F6]with text:Roadmap refresh pending — <plan-or-audit-or-decision-path> (date: YYYY-MM-DD) post-dates <roadmap-file> and may indicate completed/changed phases.
- Include up to 3 pointer paths per roadmap finding.
- Never auto-edit checkboxes. The user reviews and updates.
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.
- 4d ago First seen · 88 lines · 18 tokens per session scan A 77fe5aea9b8a
freshness-checker is an agent published in the GitHub repository yacb2/aidex (2 stars, last pushed 7d ago), licensed MIT. It adds 18 tokens to every session and 791 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
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-scope-coordinator
L1 scope coordinator - drives the useful-first adaptive roadmap flow and returns one independently approved executable ROADMAP.md before build.
ap-scoper
L3 useful-first roadmap author or complementary scout - proves capability when needed, inspects the real repository, and contributes to one executable ROADMAP.md without spawning.