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/wdhwg001/csift/agents-mdgit clone --depth 1 https://github.com/wdhwg001/csiftWrote 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/wdhwg001/csift/agents-md)<a href="https://agentmods.dev/instructions/wdhwg001/csift/agents-md"><img src="https://agentmods.dev/badge/instructions/wdhwg001/csift/agents-md.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.30399 | $0.30399 |
| Opus 5 | $0.15199 | $0.15199 |
| Sonnet 5 | $0.06080 | $0.06080 |
| Haiku 4.5 | $0.03040 | $0.03040 |
Grade A, and why
csift 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 today.
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 — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - csift operating manual
Project-specific operating manual for any AI agent (Claude Code, Codex, Cursor) working in this repo. Read this first when a conversation opens. This file is sufficient for repo mechanics + invariants - directory map, dispatch wiring, test harness, the rules you must not break - so a fresh mid-size model can add/modify a subcommand or fix a bug respecting every invariant without spelunking the source. For the exact behavioural contract of a subcommand (precise flag semantics, output shape, edge cases), open the matching SPEC.md section 6 subsection; SPEC is the authority on what each command does, this file on how to work in the repo.
About this file.
AGENTS.mdis the canonical, vendor-neutral filename.CLAUDE.mdis a symlink toAGENTS.md- editAGENTS.mdonly; the symlink follows. Companion doc:SPEC.md(~175KB / ~1240 lines) is the product/behaviour spec - open it whenever you change search/verbatim/recover/etc. behaviour. Concrete pointers: SPEC section 4 = record semantics, section 5 = the full label taxonomy (search -trole.class.sub), section 6 = per-subcommand specifications (flags, output shape, edge cases), section 7 = the performance contract, section 8.2 = the JSON envelope v2;## 6 Subcommand specificationsopens with the per-version CHANGE LEDGERS, ordered newest-first (the newest entry is authoritative; historical entries describe their own versions' surfaces). This file = how to work in the repo; SPEC.md = what to build. The FIVE-DOCUMENT CONTRACT (user-ruled, v0.5.1):SKILL.md= the LLM manual (density + weak-attention retrievability) ·--help= the human (CLI-proficient) manual — INFORMATION-PARITY with SKILL, never thinner, but plain prose with stronger structure/layout (help IS surface: changing it bumps the version triple) ·README.md= promotion ·SPEC.md= design intent · this file = maintenance. When code and a doc disagree, code wins - re-verify, then fix the doc.
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.
- today Changed · +66 lines · +5,546 tokens per session d11eee417921
- 4d ago First seen · 306 lines · 24,853 tokens per session scan A 0655ab1f64f8
csift AGENTS.md is an instructions file published in the GitHub repository wdhwg001/csift (29 stars, last pushed today), licensed MIT. It adds 30,399 tokens to every session, about $0.1520 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
recursive-decomposition-skill AGENTS.md
Instructions for massimodeluisa/recursive-decomposition-skill, covering agents: recursive-decomposition skill, read these first (mandatory), language policy, non-negotiables and commands.
self-review CLAUDE.md
Claude Code instructions for HoussemDjeghri/self-review, covering self-review — working notes for this repository, plugin/ is the product; everything beside it is not, ./test.sh is the gate, claims in the docs are enforced, not asserted and releasing.
skills AGENTS.md
AGENTS.md instructions for foyzulkarim/skills, covering agents.md — foyzulkarim/skills, repo nature, developer commands, local testing workflow (scripts/sync-skills.sh) and pipeline artifacts on master.
timbogp-marketplace CLAUDE.md
Instructions for TimboGP/timbogp-marketplace: This file is kept as a compatibility pointer for Claude Code.
ClaudeMarketplace CLAUDE.md
Claude Code instructions for RealDougEubanks/ClaudeMarketplace, covering claude code skills marketplace — project context, contribution conventions, pre-commit checklist (mandatory — run before every commit) and golden rules.
qector-claude-plugin AGENTS.md
AGENTS.md instructions for GuillaumeLessard/qector-claude-plugin, covering policylayer playbook, repository guidelines, project structure & module organization, build, test, and development commands and coding style & naming conventions.