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/cynrath/agent-context-kit/copilot-instructionsgit clone --depth 1 https://github.com/Cynrath/agent-context-kitWhat 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.00758 | $0.00758 |
| Opus 5 | $0.00379 | $0.00379 |
| Sonnet 5 | $0.00152 | $0.00152 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
agent-context-kit 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.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions
Prefer minimal, tested, secure changes that follow the project docs and task files.
Maintenance Note
This file is hand-maintained. ackit generate does not regenerate it. Update it through a regular docs/tasks/ task and a normal commit, never through the generator.
Governance
- Authoritative agent policy:
AGENTS.md— controlled-release governance. - Release actions (
masterpush/merge, npm publish, tags, GitHub Releases) are user-authorized only; they require explicit authorization inside the active task. Always prohibited: force-push, history rewrite, tag movement/deletion, workflow dispatch, deployments. - Canonical development branch is
master;rebuild/ackit-vnextis retired (historical evidence only, do not push).
Workflow
- Task-first workflow is mandatory. Every implementation change starts from a task record under
docs/tasks/active/, created withnode dist/cli/index.js task "<title>".
Commit Completeness Hard Rule
- Before any push, run
git statusand confirm the working tree is clean. - Never leave a newly created
.mdtask file, plan, queue row, or test file uncommitted. New files must be added and committed in the same logical commit that creates them, or in an immediately following commit, before any push.
Repository Health
- README: yes
- LICENSE: yes
- SECURITY: yes
- Tests: yes
- CI: yes
- Agent instructions: yes
Stack & Validation
- Main stack: TypeScript (strict ESM) + Node.js >= 22, pnpm, Vitest, Biome.
- All validation uses the repository-built CLI:
node dist/cli/index.js <command>. The old global .NETackittool anddotnet runinvocations are not valid validation tools on this branch.
Release Status
- Current line: AgentContextKit, package
@cynrath/agent-context-kit, version0.2.0onmaster(tagv0.2.0, npmlatest → 0.2.0, GitHub Releasev0.2.0);0.1.1/0.1.0remain as historical releases. - npm publish, tag creation, GitHub Releases, and other master mutations require explicit user authorization. Automated publishing runs only through the tag-triggered
.github/workflows/release.ymlafter that authorization; master pushes never publish. - Legacy .NET line is frozen and immutable: NuGet
AgentContextKit1.0.0-rc.1(exact tag/release/assets/attestations at repository commit258918b33c3d1359aac967604ee524e8b66ddf02) and earlier prereleases remain untouchable; do not republish, reuse, move, replace, or delete them. Historical failed recovery evidence remains preserved.
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 · 48 lines · 758 tokens per session scan A 8d411ec36b1c
agent-context-kit copilot-instructions.md is an instructions file published in the GitHub repository Cynrath/agent-context-kit (14 stars, last pushed 3d ago), licensed MIT. It adds 758 tokens to every session, about $0.0038 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 instructions, from other repositories
repository-harness AGENTS.md
Instructions for hoangnb24/repository-harness, covering agent instructions and harness.
repository-harness CLAUDE.md
Instructions for hoangnb24/repository-harness, covering project rules and harness.
boring-is-all-you-need AGENTS.md
Instructions for Khalilzhang0825/boring-is-all-you-need, covering agents.md - boring is all you need codex guide, project intent, working rules, validation and release discipline.
AGENTS.md AGENTS.md
Instructions for Anbeeld/AGENTS.md, covering global instructions, priorities, boundaries, uncertainty and evidence.
vibe-coding-repository-standard AGENTS.md
Instructions for cz1993/vibe-coding-repository-standard, covering vcrs repository instructions, purpose, communication, change discipline and privacy and safety.
AgentRules AGENTS.md
Instructions for LearnAIHubC/AgentRules, covering agents.md, 1. think before coding, 2. simplicity first, 3. preserve existing architecture and framework boundaries and 4. surgical changes.