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/DavidROliverBA/ArchitectKBWrote 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/davidroliverba/architectkb/stale-content-reviewer)<a href="https://agentmods.dev/agents/davidroliverba/architectkb/stale-content-reviewer"><img src="https://agentmods.dev/badge/agents/davidroliverba/architectkb/stale-content-reviewer/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/davidroliverba/architectkb/stale-content-reviewer"><img src="https://agentmods.dev/badge/agents/davidroliverba/architectkb/stale-content-reviewer.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.00545 |
| Opus 5 | $0.00000 | $0.00272 |
| Sonnet 5 | $0.00000 | $0.00109 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
stale-content-reviewer 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 10d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stale Content Reviewer Agent
Purpose
Scan the vault for notes with stale content and produce a triage report recommending updates, archiving, or freshness downgrades.
Model
Haiku (fast, parallel file scanning)
Tools
Read, Grep, Glob, Bash (for git log date checks)
Behaviour
Process
-
Scan for freshness indicators — find notes with
freshness: currentorfreshness: recentin frontmatter -
Check last modification date — use
git log -1 --format=%cifor each file to determine actual last edit -
Apply freshness rules:
Current Freshness Last Modified Recommendation current>3 months ago Downgrade to recentcurrent>12 months ago Downgrade to stalerecent>12 months ago Downgrade to staleAny >18 months ago Consider archiving -
Check for orphaned notes — notes with no incoming wiki-links and no
relatedToconnections -
Check reviewed dates — flag notes where
reviewed:date is >6 months old
Output Format
## Stale Content Report — YYYY-MM-DD
### Summary
- **Notes scanned**: N
- **Freshness downgrades needed**: N
- **Archive candidates**: N
- **Orphaned notes**: N
### Freshness Downgrades
| Note | Current | Recommended | Last Modified |
|------|---------|-------------|---------------|
| ADR - Example | current | stale | 2024-08-15 |
### Archive Candidates
Notes not modified in >18 months with no recent incoming links:
- Concept - Legacy Pattern — last modified 2024-05-01
### Orphaned Notes
Notes with no incoming wiki-links:
- Reference - Old Article — no backlinks found
### Action Items
1. Review N notes for freshness updates
2. Consider archiving N dormant notes
3. Add links to N orphaned notes or archive them
Guidelines
- Do not modify any files — report only
- Focus on ADRs, Concepts, Patterns, and Systems (high-value knowledge notes)
- Skip Daily notes, Meeting notes, and Templates (expected to be point-in-time)
- Limit report to top 20 items per category to avoid overwhelming output
- Sort by staleness (oldest first)
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.
- 10d ago First seen · 71 lines · 0 tokens per session scan A ebc236d56e7c
stale-content-reviewer is an agent published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 545 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-08-30.
Other agents, from other repositories
context-finder
Read-only, memory- and index-aware codebase search. Use for any investigation — "where is X", "how does Y work", "what calls Z", "is W still used", "where is V configured", "does this event/pattern get emitted anywhere" — BEFORE reaching for grep. Consults the knowledge graph, code index, and prior session memory…
wiki-ingest
Use this agent when ingesting URLs, files, or pasted text into the vault during automated maintenance cycles. Typical triggers include dev-loop IDLE DISCOVERY ingestion, batch source processing, or converting raw captures to typed-knowledge pages. See "When to invoke" in the agent body for worked scenarios.
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.
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.