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/bomly-dev/bomly-cli/copilot-instructionsgit clone --depth 1 https://github.com/bomly-dev/bomly-cliWhat 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.00032 | $0.00032 |
| Opus 5 | $0.00016 | $0.00016 |
| Sonnet 5 | $0.00006 | $0.00006 |
| Haiku 4.5 | $0.00003 | $0.00003 |
Grade A, and why
bomly-cli 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 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
Copilot Instructions\n\nSee AGENTS.md — that is the single source of truth for agent instructions in this repo.
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 · 1 lines · 32 tokens per session scan A 04688289f467
bomly-cli copilot-instructions.md is an instructions file published in the GitHub repository bomly-dev/bomly-cli (11 stars, last pushed 3d ago), licensed Apache-2.0. It adds 32 tokens to every session, about $0.0002 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
kc-secure-repo-template AGENTS.md
AGENTS.md instructions for CaseyLabs/kc-secure-repo-template, covering agents.md, project overview, project defaults, public interface and skill routing.
gh-guard CLAUDE.md
Instructions for sbom-tool/gh-guard, covering gh-guard: ci/cd supply chain hardening for rust, what this plugin does, hardening levels, commands and skills (contextual knowledge).
kc-secure-repo-template CLAUDE.md
Claude Code instructions for CaseyLabs/kc-secure-repo-template, a project described as: Security-hardened GitHub repository template, designed to prevent supply-chain attacks. Includes vulnerability scanning and AI agent skills.
Tracely-ai CLAUDE.md
Claude Code instructions for Jwuthri/Tracely-ai, covering claude.md, commands, architecture, hard rules and gotchas.
devopness AGENTS.md
Instructions for devopness/devopness, covering agents, core flow, shared constraints, monorepo structure and git workflow.
devopness CLAUDE.md
Instructions for devopness/devopness, a project described as: Devopness: AI DevOps on your cloud. Deploy apps, infra and CI/CD. Any cloud and any stack, one MCP. Deterministic API, opinionated and fully configurable. No cloud credentials in AI chats. Free plan.