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/marconae/speq-skill/claude-mdgit clone --depth 1 https://github.com/marconae/speq-skillWrote 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/marconae/speq-skill/claude-md)<a href="https://agentmods.dev/instructions/marconae/speq-skill/claude-md"><img src="https://agentmods.dev/badge/instructions/marconae/speq-skill/claude-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.00592 | $0.00592 |
| Opus 5 | $0.00296 | $0.00296 |
| Sonnet 5 | $0.00118 | $0.00118 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
speq-skill 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 4d 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 — 22 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local Development Rules
You are building speq-skill while using it: the skills in .claude/skills/ are simultaneously this repo's dev tooling and the source that scripts/plugin/build.sh compiles into the Claude and Codex plugin.
Rules
- CLI: always invoke the local build —
./target/debug/speq <cmd>(or./target/release/speq <cmd>after a release build). Never the globalspeqorcargo run --. - Skill names are context-specific:
/speq-*in this repo,/speq:*in the installed plugin.build.shperforms thespeq-*→speq:*rename, drops thespeq-folder prefix, and stamps version + author fromCargo.toml. - Version:
Cargo.tomlis the single source of truth.scripts/lib/version.sh(get_version) feedsbuild.shand the docker tests — never hard-code the version anywhere else. - Tests: integration tests SHALL use fixtures under
tests/fixtures/, not inline spec strings. - Git:
git-agentis the only agent permitted to write git history or touch a remote; every other agent is read-only. - Commits follow Conventional Commits —
<type>[scope]: <description>(+ optional body/footer). Types:feat(MINOR),fix(PATCH),perf,refactor,test,docs,spec,chore. Breaking change =!after type/scope or aBREAKING CHANGE:footer (MAJOR). - Expert tasks:
planner-agentmarks reasoning-heavytasks.mdlines[expert];speq-implementroutes those toimplementer-expert-agent, the rest toimplementer-agent. Tag sparingly. - Model routing is hardcoded in each skill/agent frontmatter and stamped by
build.sh— seedocs/model-routing.md. - Markdown prose: never artificially word-wrap prose in Markdown files. Write one logical line per paragraph and list item (soft-wrap) so diffs stay line-per-thought and reflows don't churn. Do not join fenced code, tables, ASCII diagrams, YAML frontmatter, or structured
**Field:**lines. - Mission scope:
specs/mission.mdis the mission for thespeqCLI only — not for the skills. Skill purpose and intent live in the skill files anddocs/.
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.
- 4d ago First seen · 22 lines · 592 tokens per session scan A 486b5823faf5
speq-skill CLAUDE.md is an instructions file published in the GitHub repository marconae/speq-skill (50 stars, last pushed 1mo ago), licensed MIT. It adds 592 tokens to every session, about $0.0030 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
spec-superflow GEMINI.md
Gemini CLI instructions for MageByte-Zero/spec-superflow, covering spec-superflow and spec-superflow v1.2.0 | 阶段: {{state}} | 工作流: {{workflow}}.
spec-superflow copilot-instructions.md
Copilot instructions for MageByte-Zero/spec-superflow, covering phase guard, ✅ 允许操作, ⛔ 禁止操作 and 🔔 决策点.
blueprint CLAUDE.md
Instructions for owainlewis/blueprint, a project described as: The best agent skills in the world for software development.
spec_driven_develop CLAUDE.md
Instructions for zhu1090093659/spec_driven_develop: Read AGENTS.md first. It is the shared project-level instruction source for Codex, OpenCode, Cursor, Claude Code, and other Markdown-aware coding agents.
cafleet CLAUDE.md
Claude Code instructions for himkt/cafleet, covering claude.md, skills, project: cafleet, tech stack and commands.
mine AGENTS.md
AGENTS.md instructions for 6ixGODD/mine, covering agent working agreement, source of truth, design rules, no historical baggage by default and document boundaries.