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/psychquant/che-ical-mcp/agents-mdgit clone --depth 1 https://github.com/PsychQuant/che-ical-mcpWrote 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/psychquant/che-ical-mcp/agents-md)<a href="https://agentmods.dev/instructions/psychquant/che-ical-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/psychquant/che-ical-mcp/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.00283 | $0.00283 |
| Opus 5 | $0.00142 | $0.00142 |
| Sonnet 5 | $0.00057 | $0.00057 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
che-ical-mcp 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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- che-apple-mail-mcp AGENTS.md — 100% identical, 0 lines differ
What it actually says
Spectra Instructions
This project uses Spectra for Spec-Driven Development(SDD). Specs live in openspec/specs/, change proposals in openspec/changes/.
Use $spectra-* skills when:
- A discussion needs structure before coding →
$spectra-discuss - User wants to plan, propose, or design a change →
$spectra-propose - Tasks are ready to implement →
$spectra-apply - There's an in-progress change to continue →
$spectra-ingest - User asks about specs or how something works →
$spectra-ask - Implementation is done →
$spectra-archive
Workflow
discuss? → propose → apply ⇄ ingest → archive
discussis optional — skip if requirements are clear- Requirements change mid-work?
ingest→ resumeapply
Parked Changes
Changes can be parked（暫存）— temporarily moved out of openspec/changes/. Parked changes won't appear in spectra list but can be found with spectra list --parked. To restore: spectra unpark <name>. The $spectra-apply and $spectra-ingest skills handle parked changes automatically.
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.
- 5d ago First seen · 28 lines · 283 tokens per session scan A 9165179e5f8a
che-ical-mcp AGENTS.md is an instructions file published in the GitHub repository PsychQuant/che-ical-mcp (36 stars, last pushed 4d ago), licensed MIT. It adds 283 tokens to every session, about $0.0014 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
Skill_Seekers CLAUDE.md
Instructions for yusufkaraaslan/Skill_Seekers, covering claude.md, project overview, essential commands, required before running tests or cli (src/ layout) and run all tests (never skip - all must pass before commits).
claude-code-apple-skills CLAUDE.md
Claude Code instructions for rshankras/claude-code-apple-skills, covering claude.md, repository purpose, architecture, skill structure and yaml frontmatter (required).
octocode CLAUDE.md
Claude Code instructions for bgauryy/octocode: Read AGENTS.md. Discover repository skills under .agents/skills and activate only those matching the task.
ai-workflow AGENTS.md
Instructions for cunhaax/ai-workflow, covering ai workflow template, rules — non-negotiable, project overview, commands and architecture.
substack-mcp-plus CLAUDE.md
Instructions for ty13r/substack-mcp-plus, covering claude.md, quick command reference (use these!), always activate virtual environment first, run tests (use python3!) and code quality.
claude-code-skill-factory CLAUDE.md
Instructions for alirezarezvani/claude-code-skill-factory, covering claude.md - skills factory orchestration, repository purpose, modular claude.md architecture, navigation map and repository structure.