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 commands/ivbeg/newsworker/cachegit clone --depth 1 https://github.com/ivbeg/newsworkerWhat 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.00005 | $0.00120 |
| Opus 5 | $0.00003 | $0.00060 |
| Sonnet 5 | $0.00001 | $0.00024 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
cache 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 2d 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
cache
Inspects or clears the spec and content caches. See Settings.
newsworker cache stats # entry counts and total size per cache
newsworker cache list # list cached entries
newsworker cache clear # delete all cached specs and content
newsworker cache clear --content # scope to a single cache (--specs / --content)
--config / -c selects the settings file that determines cache_dir.
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.
- 2d ago First seen · 18 lines · 5 tokens per session scan A c7ca35ebc5a0
cache is a command published in the GitHub repository ivbeg/newsworker (87 stars, last pushed 12d ago), licensed MIT. It adds 5 tokens to every session and 120 once invoked, about $0.0000 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 commands, from other repositories
release-prepare
Require one explicit semantic version argument. Refuse an existing published version or Git tag.
release-verify
Read AGENTS.md, the entire .agents/PRIVATERELEASEPLAN.md, .agents/FAILURERETROSPECTIVE.md, and docs/releasing.md. Inspect the worktree and version-bearing files first.
OPSX: Archive
Archive a completed change in the experimental workflow.
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.