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 instructions/weskerllc/cronicorn/testing-strategygit clone --depth 1 https://github.com/weskerllc/cronicornWrote 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/instructions/weskerllc/cronicorn/testing-strategy)<a href="https://agentmods.dev/instructions/weskerllc/cronicorn/testing-strategy"><img src="https://agentmods.dev/badge/instructions/weskerllc/cronicorn/testing-strategy.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.01132 | $0.01132 |
| Opus 5 | $0.00566 | $0.00566 |
| Sonnet 5 | $0.00226 | $0.00226 |
| Haiku 4.5 | $0.00113 | $0.00113 |
Grade A, and why
cronicorn testing-strategy.instructions.md 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 175 lines · 1,132 tokens per session scan A 8837a03f73f5
cronicorn testing-strategy.instructions.md is an instructions file published in the GitHub repository weskerllc/cronicorn (3 stars, last pushed 6mo ago), with no licence file. It adds 1,132 tokens to every session, about $0.0057 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 instructions, from other repositories
gocron AGENTS.md
Instructions for flohoss/gocron, covering agent guidance, principles, tooling — always via docker compose, never on the host, common commands and compose pinned versions.
nginx-ui CLAUDE.md
Claude Code instructions for 0xJacky/nginx-ui, covering nginx ui - claude code guidelines, package manager, backend (go) development, technologies & frameworks and code organization.
nginx-ui AGENTS.md
AGENTS.md instructions for 0xJacky/nginx-ui, a project described as: Yet another WebUI for Nginx.
dagu CLAUDE.md
Claude Code instructions for dagucloud/dagu, covering dagu repository guide, project, repository map, runtime flow and architecture rules.
dagu AGENTS.md
AGENTS.md instructions for dagucloud/dagu, a project described as: Self-hostable workflow orchestrator for teams whose main work isn't orchestration. Declarative YAML over your scripts, SSH commands, containers, etc; keep workflows separate from business logic. One binary, no database, runs on limited H/W resources.…
leo CLAUDE.md
Instructions for blackpaw-studio/leo, covering repository agent guidance, what is leo, build & test commands, run a single test and coverage report.