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/kulesh/recurgent/copilot-instructionsgit clone --depth 1 https://github.com/kulesh/recurgentWrote 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/kulesh/recurgent/copilot-instructions)<a href="https://agentmods.dev/instructions/kulesh/recurgent/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/kulesh/recurgent/copilot-instructions.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.00109 | $0.00109 |
| Opus 5 | $0.00055 | $0.00055 |
| Sonnet 5 | $0.00022 | $0.00022 |
| Haiku 4.5 | $0.00011 | $0.00011 |
Grade A, and why
recurgent copilot-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.
What it actually says
Issue Tracking
This project uses bd (beads) for issue tracking.
Run bd prime for workflow context, or install hooks (bd hooks install) for auto-injection.
Quick reference:
bd ready- Find unblocked workbd create "Title" --type task --priority 2- Create issuebd close <id>- Complete workbd sync- Sync with git (run at session end)
For full workflow details: bd prime
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 · 13 lines · 109 tokens per session scan A 18f00dbc82a6
recurgent copilot-instructions.md is an instructions file published in the GitHub repository kulesh/recurgent (5 stars, last pushed 6d ago), licensed MIT. It adds 109 tokens to every session, about $0.0005 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
gini-agent AGENTS.md
AGENTS.md instructions for Open-Curiosity/gini-agent, covering gini agent instructions, shape, adrs, boundaries and branches.
pi AGENTS.md
AGENTS.md instructions for TGYD-helige/pi, covering pi extensions monorepo — agent guidelines, project overview, required agent skills, ponytail — minimal-code discipline and mattpocock/skills — engineering workflow skills.
linggen CLAUDE.md
Claude Code instructions for linggen/linggen, covering claude.md, doc and spec, build, test, run, architecture and configuration.
floom AGENTS.md
AGENTS.md instructions for floomhq/floom, covering agents.md — floom, setup (once), run, test / lint and hard rules (do not violate).
Bamboo-agent AGENTS.md
AGENTS.md instructions for bigduu/Bamboo-agent: Read README.md for the product boundary. Use this canonical Jiandu memory contract.
seshat AGENTS.md
Instructions for KPO-Tech/seshat, covering agent instructions — seshat, project overview, build and test, branching strategy and package boundary rules (critical).