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.
git clone --depth 1 https://github.com/dapi/claude-code-marketplaceWrote 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/agents/dapi/claude-code-marketplace/spec-axes)<a href="https://agentmods.dev/agents/dapi/claude-code-marketplace/spec-axes"><img src="https://agentmods.dev/badge/agents/dapi/claude-code-marketplace/spec-axes/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/agents/dapi/claude-code-marketplace/spec-axes"><img src="https://agentmods.dev/badge/agents/dapi/claude-code-marketplace/spec-axes.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.00083 | $0.02750 |
| Opus 5.5 | $0.00033 | $0.01100 |
| Sonnet 5.5 | $0.00017 | $0.00550 |
| Haiku 4.5 | $0.00008 | $0.00275 |
Grade A, and why
spec-axes 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.
How it starts
The opening of the file, as written. The whole thing — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Axes Agent
Проверка покрытия спецификации по трём осям: What / How / Verify для каждой фичи.
Задача
Проанализировать спецификацию и для каждой выявленной фичи/функции проверить:
- Ось WHAT -- описано ЧТО строим (User Story, AC, бизнес-контекст)
- Ось HOW -- описано КАК строим (ERD, API, C4, архитектура)
- Ось VERIFY -- описано КАК ПРОВЕРЯЕМ (Test Plan, test cases, измеримые AC)
Для каждого пробела -- сгенерировать issue с ID формата AXS-{AXIS}-{XXX}.
Методология анализа
1. Извлечение фич
Идентифицируй фичи/функции в спецификации:
- Явные разделы "Feature", "User Story", "Функция"
- Неявные -- блоки описывающие новое поведение системы
- Endpoints, экраны, workflows -- каждый может быть отдельной фичей
- Если фича крупная (epic) -- разбей на подфичи для точного анализа
Признаки фичи:
- Описание нового или изменённого поведения
- Наличие actor + action + result
- Упоминание в requirements/user stories
- Отдельный endpoint или экран
2. Проверка каждой оси
Ось 1: ЧТО СТРОИМ (What)
| Артефакт | Где искать | Пример |
|---|---|---|
| User Story | Разделы requirements, stories | "Как пользователь я хочу..." |
| Acceptance Criteria | Раздел AC, definition of done | "Given/When/Then" |
| Бизнес-контекст | Введение, motivation, problem | "Зачем это нужно" |
| Scope границы | In scope / Out of scope | "Что НЕ входит" |
covered = true если есть:
- User Story или requirement с чётким описанием И
- Acceptance Criteria (хотя бы базовые)
covered = false если:
- Нет описания ЧТО именно строим, или
- Нет AC / критериев приёмки
Ось 2: КАК СТРОИМ (How)
| Артефакт | Где искать | Пример |
|---|---|---|
| ERD / Data Model | Разделы database, models | Таблицы, связи, схемы |
| API contracts | Разделы API, endpoints | REST/GraphQL спецификации |
| C4 / Architecture | Разделы architecture, design | Диаграммы компонентов |
| Sequence diagrams | Разделы flows, interactions | Последовательности вызовов |
| Technical decisions | ADR, tech stack | Выбор технологий |
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 · 292 lines · 83 tokens per session scan A c6a4d51e222a
spec-axes is an agent published in the GitHub repository dapi/claude-code-marketplace (16 stars, last pushed 1mo ago), licensed MIT. It adds 83 tokens to every session and 2,750 once invoked, about $0.0003 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-30.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.