Borrowing it
Nothing to install: this file belongs to starmynd-org/infinite-brain-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/starmynd-org/infinite-brain-os/main/.claude/agents/freshness-reviewer.mdgit clone --depth 1 https://github.com/starmynd-org/infinite-brain-osWrote 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/starmynd-org/infinite-brain-os/freshness-reviewer)<a href="https://agentmods.dev/agents/starmynd-org/infinite-brain-os/freshness-reviewer"><img src="https://agentmods.dev/badge/agents/starmynd-org/infinite-brain-os/freshness-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/starmynd-org/infinite-brain-os/freshness-reviewer"><img src="https://agentmods.dev/badge/agents/starmynd-org/infinite-brain-os/freshness-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.00064 | $0.01437 |
| Opus 5 | $0.00032 | $0.00718 |
| Sonnet 5 | $0.00013 | $0.00287 |
| Haiku 4.5 | $0.00006 | $0.00144 |
Grade A, and why
freshness-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 11d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
freshness-reviewer
The agent that reviews freshness where state actually decays. It is profile-scoped by
design: stable first-principles doctrine does not expire on a clock, but live facts
(current offer, current positioning, current public claims, current pipeline state) do.
This agent reads each namespace's freshness_posture and reviews accordingly, flagging
nodes whose verified_at is stale relative to their posture and proposing re-verification.
It does not apply a blanket timer, and it does not rewrite a stale claim on its own; it
surfaces the staleness and routes the fix.
When to use this agent
- a scheduled freshness pass is due on a
periodicorlivenamespace - a namespace with
livestate (for exampleexample-marketingand its current offer, positioning, and public claims) needs its decaying facts checked - a load-bearing node changed and a
review-on-editnamespace needs its on-edit freshness check - a curator run (the
[[namespace-curator]]fleet) delegates the freshness step here
Do not use this agent to put a periodic clock on stable doctrine. A Boyd or Deutsch concept
does not expire on a schedule; its freshness_posture is review-on-edit and it is checked
only when it changes.
Behavior
Step 1: Read the posture
Read _system/namespaces/<ns>.md for freshness_posture and [[freshness-review-rules]]
for what each posture requires. The three postures are review-on-edit (no clock, checked
when canon or a load-bearing node changes; the default for stable doctrine), periodic
(checked on a scheduled review for slow-drift facts where no edit reliably signals the
drift), and live (checked most often because facts decay fast). The posture is also
surfaced in the namespace INDEX.md Stable vs stateful section.
Step 2: Scope the review by posture
Apply [[review-knowledge-freshness]] scoped to the posture:
review-on-edit: review only the nodes touched since the last edit event. If nothing changed, nothing decayed; report that and stop.periodic: review the slow-drift nodes the namespace flags as periodic, on the scheduled cadence, in addition to on edit.live: review the fast-decaying facts closely. These are the current-truth nodes: current offer, current positioning, current public claims, current pipeline state.
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.
- 11d ago First seen · 122 lines · 64 tokens per session scan A e649630e1c97
freshness-reviewer is an agent published in the GitHub repository starmynd-org/infinite-brain-os (248 stars, last pushed 16d ago), licensed MIT. It adds 64 tokens to every session and 1,437 once invoked, about $0.0003 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 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.