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/sequant-io/sequant/claude-mdgit clone --depth 1 https://github.com/sequant-io/sequantWhat 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.00400 | $0.00400 |
| Opus 5 | $0.00200 | $0.00200 |
| Sonnet 5 | $0.00080 | $0.00080 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
sequant CLAUDE.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 yesterday.
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
Sequant
Commit Rules
- Do NOT add
Co-Authored-Bylines to any commits in this repository.
Hooks
HOOK_BLOCKED: Force push— see .claude/skills/_shared/references/force-push.md for the user-handoff pattern. Do not attemptCLAUDE_HOOKS_DISABLED=truebypasses; they don't work.
Skills
- When invoking a sequant skill via
Skill(skill: "<name>", ...)from inside another sequant skill, qualify names that collide with Anthropic top-level skills asSkill(skill: "sequant:<name>", ...). Bare colliding names silently misroute to Anthropic's version. Enforced in CI bynpm run lint:skill-calls(scripts/lint-skill-calls.ts). See #562 / #568.
Testing
- Gate tests ship with a recorded mutation result. A test whose job is to gate a claim — a fixture exists, a skill section is present, a flag is wired — must be mutation-verified before it counts as coverage: delete the thing it asserts, confirm exactly that test fails, restore, and record the result using the
Mutation-verified: AC-N — <mutation>; <test> failed; restored.marker format (machine-anchored as<!-- SEQUANT_MUTATION: {"ac":"AC-N","mutation":"...","failedTest":"..."} -->) in the PR body —/qa§6i parses and enforces this record for gate-test ACs. Scope file-reading assertions to the delimited region they mean to check; matching the whole file lets a doc header or comment satisfy the assertion. See #830, where deleting the injection fixture's payload left the suite green, and #939, which promoted this record from prose to a parseable gate.
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.
- yesterday First seen · 18 lines · 400 tokens per session scan A 47c02c14db48
sequant CLAUDE.md is an instructions file published in the GitHub repository sequant-io/sequant (1 stars, last pushed 2d ago), licensed MIT. It adds 400 tokens to every session, about $0.0020 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
agent-estate AGENTS.md
AGENTS.md instructions for MercuriusDream/agent-estate, covering agents.md, project structure, claude code plugin conventions, plugin manifest (.claude-plugin/plugin.json) and commands (commands/.md).
claude_code_vs CLAUDE.md
Instructions for firish/claude_code_vs, covering claude.md, what this is, working agreement (how we collaborate here), architecture (where things live) and tech stack & hard constraints.
dev-agent-skills CLAUDE.md
Instructions for fvadicamo/dev-agent-skills, covering claude.md, project overview, architecture, key file: marketplace.json and skill anatomy.
ob-1 AGENTS.md
Instructions for Overbrilliant/ob-1, covering agents.md, project index, stack, commands and key files.
browser-agent CLAUDE.md
Instructions for uiuing/browser-agent, a project described as: An open-source AI agent for the browser. Bring any model. It plans in the side panel, acts on real pages through tools, and verifies every claimed result against the live DOM — with guardrails and reusable skills.
lihongwei-cn CLAUDE.md
Instructions for LiHongwei-cn/lihongwei-cn, covering claude.md — claude code 项目记忆, 用户身份, 回复风格(红线), 网站 and 技术栈.