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/ssbun/csl-agent-kit/agents-mdgit clone --depth 1 https://github.com/SSBun/csl-agent-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.00295 | $0.00295 |
| Opus 5 | $0.00148 | $0.00148 |
| Sonnet 5 | $0.00059 | $0.00059 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
csl-agent-kit AGENTS.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
Project Agent Rules
Rule Changes
- After modifying any skill package under
skills/or.agents/skills/, load the built-inskill-qualitySkill and runnode skills/meta/skill-quality/scripts/check.js <skill-dir>from the workspace root for every changed package before claiming completion. Use--all --workspace .only for broad Skill changes. Quality failures block completion; review and disclose any accepted warning that affects confidence. - After modifying non-skill rules (AGENTS.md, CLAUDE.md, SOPs under
~/.csl-agent-kit/sops/orskills/meta/agent-sops/sops/, hooks),skill-qualitydoes not apply. Verify instead by: (1) structural consistency with existing files of the same kind, and (2) for SOPs — matching the YAML header fields and section template of peer SOPs. Runadversarial-reviewor request human review only when the user explicitly asks for that review; high risk alone does not trigger it.
Task Files
- Store each task in
tasks/tasks/<task-slug>.mdand add its title, current status, and relative link at the top of the newest-firsttasks/tasks.mdindex. - Update only the owning task file and its exact index entry; do not rewrite unrelated task records. Add new lessons at the top of
tasks/lessons.md.
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 · 12 lines · 295 tokens per session scan A ff4a4c9fd091
csl-agent-kit AGENTS.md is an instructions file published in the GitHub repository SSBun/csl-agent-kit (10 stars, last pushed 3d ago), licensed MIT. It adds 295 tokens to every session, about $0.0015 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
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.