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 skills add victorgrein/spec-crew --skill core-buildgit clone --depth 1 https://github.com/victorgrein/spec-crewWrote 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/skills/victorgrein/spec-crew/core-build)<a href="https://agentmods.dev/skills/victorgrein/spec-crew/core-build"><img src="https://agentmods.dev/badge/skills/victorgrein/spec-crew/core-build/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/victorgrein/spec-crew/core-build"><img src="https://agentmods.dev/badge/skills/victorgrein/spec-crew/core-build.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00038 | $0.02244 |
| Opus 5.5 | $0.00015 | $0.00898 |
| Sonnet 5.5 | $0.00008 | $0.00449 |
| Haiku 4.5 | $0.00004 | $0.00224 |
Grade A, and why
core-build 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 1mo 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
19 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/starter/.env.example 365 B
- assets/starter/config/agents.yaml 639 B
- assets/starter/config/tasks.yaml 731 B
- assets/starter/crew.py 1.0 KB runs code
- assets/starter/main.py 640 B runs code
- assets/starter/README.md 553 B
- assets/templates/agents-advanced.yaml 2.9 KB
- assets/templates/agents-basic.yaml 639 B
- assets/templates/tasks-advanced.yaml 4.0 KB
- assets/templates/tasks-basic.yaml 731 B
- references/api/agents.md 3.7 KB
- references/api/crews.md 5.2 KB
- references/api/tasks.md 4.6 KB
- references/external.md 658 B
- references/guides/best-practices.md 8.2 KB
- references/guides/patterns.md 9.5 KB
- scripts/generate_config.py 7.4 KB runs code
- scripts/scaffold_crew.py 4.1 KB runs code
- scripts/validate_crew.py 18 KB runs code
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.
- 1mo ago First seen · 363 lines · 38 tokens per session scan A 8dfa8a325c93
core-build is a skill published in the GitHub repository victorgrein/spec-crew (7 stars, last pushed 8mo ago), with no licence file. It adds 38 tokens to every session and 2,244 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
feature-dev
Take one new feature slice from idea to reviewed, committed code in a single guided pass — scope it into the smallest shippable slice, build it test-first with strict TDD, review and fix the diff, then commit it. Chains slice → test-driven-development → the built-in /code-review → git-commit. Not for reviewing an…
test-driven-development
Strict red-green-refactor TDD workflow for implementing features, fixing bugs, or changing behavior in Rails applications. Enforces the discipline of writing a failing test before any production code. Use whenever you want to implement with TDD — whether a new feature, a bugfix, a refactor, or any behavior change.
git-commit
Turn the working changes into one or more atomic commits with well-written messages. Use whenever the user runs /git-commit or asks to commit their work, wrap up a feature, or "commit what I have.".
csift
Reads, searches and counts Claude Code session transcripts (the .jsonl files under /.claude/projects, subagents too) with the csift command-line tool, and ships hooks that re-inject compacted turns or record pending questions. Use when asked what a past or running session said, did, edited, spent or is doing now; when…
recursive-decomposition
Decompose dense codebase-wide, multi-document, PDF, and aggregation work even when the input fits the context window, following Recursive Language Models (Zhang, Kraska, Khattab, 2025). Use when the user asks to analyse all files, a whole repo, all docs, large PDFs, or to aggregate or multi-hop across scattered…
socratic-review
Socratic code review and refactoring session — whether it's your own code, a teammate's PR, or something you inherited. Leads you to see the issues through questions, names smells and moves precisely, then closes with a concrete plan.