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 skills/marconae/speq-skill/speq-code-toolsnpx skills add marconae/speq-skill --skill speq-code-toolsgit clone --depth 1 https://github.com/marconae/speq-skillWhat 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.00060 | $0.00381 |
| Opus 5 | $0.00030 | $0.00191 |
| Sonnet 5 | $0.00012 | $0.00076 |
| Haiku 4.5 | $0.00006 | $0.00038 |
Grade A, and why
speq-code-tools 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 3d 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
Code Tools
Semantic code navigation and editing via Serena MCP.
Tool Preference
| Task | Use | Not |
|---|---|---|
| List directory | list_dir |
ls, find |
| Find files | find_file |
find, rg --files |
| File symbols | get_symbols_overview |
rg "class|function" |
| Symbol definition | find_symbol |
rg "function foo" |
| Symbol references | find_referencing_symbols |
rg "foo(" |
| Update function | replace_symbol_body |
read/edit/write |
| Insert after | insert_after_symbol |
read/edit/write |
| Insert before | insert_before_symbol |
read/edit/write |
| Rename symbol | rename_symbol |
rg + manual edits |
Reflection Checkpoints
Apply the Feynman Technique — explain your understanding before proceeding. Call these tools at key moments:
| Tool | When |
|---|---|
think_about_collected_information |
After exploration sequence |
think_about_task_adherence |
Before writing code |
think_about_whether_you_are_done |
Before reporting completion |
Workflow
Explore → find_symbol, get_symbols_overview
Understand → find_referencing_symbols
Reflect → think_about_collected_information
Edit → replace_symbol_body, insert_*_symbol
Verify → find_referencing_symbols
Complete → think_about_whether_you_are_done
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.
- 3d ago First seen · 44 lines · 60 tokens per session scan A 09a78ca9dba3
speq-code-tools is a skill published in the GitHub repository marconae/speq-skill (50 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 381 once invoked, about $0.0003 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 skills, from other repositories
build-executor
Govern implementation from an approved execution contract. Invoke when execution-contract.md is approved and the user wants disciplined build work, TDD execution, or guarded batch-by-batch implementation.
workflow-start
Primary entry point for the spec-superflow state-machine workflow. Invoke when the user is inside an active spec-superflow change directory (look for .spec-superflow.yaml, changes/ /, proposal.md, specs/, design.md, tasks.md, or execution-contract.md) and asks to start, continue, resume, implement, plan, or figure out…
release-archivist
Close out a spec-superflow change with verification, summary, and archive readiness. Invoke when implementation is complete, verification is underway, or the user asks for a final wrap-up.
bug-investigator
Use when encountering any bug, test failure, or unexpected behavior during spec-superflow execution, before proposing fixes. Invoked automatically when build-executor hits a blockage.
spec-writer
Create or refine spec-superflow planning artifacts. Invoke when the change is understood well enough to write proposal.md, specs/, design.md, and tasks.md.
contract-builder
Convert approved planning artifacts into an execution contract. Invoke when the user wants to start building, asks to move from planning to implementation, or when execution-contract.md is missing or stale.