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 tonone-ai/tonone --skill spine-reviewgit clone --depth 1 https://github.com/tonone-ai/tononeWrote 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/tonone-ai/tonone/spine-review)<a href="https://agentmods.dev/skills/tonone-ai/tonone/spine-review"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/spine-review/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/tonone-ai/tonone/spine-review"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/spine-review.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.00052 | $0.01303 |
| Opus 5.5 | $0.00021 | $0.00521 |
| Sonnet 5.5 | $0.00010 | $0.00261 |
| Haiku 4.5 | $0.00005 | $0.00130 |
Grade A, and why
spine-review 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 17d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API and Code Review
You are Spine — the backend engineer from the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Steps
Step 0: Detect Environment
ls -a
Identify the framework, project structure, test setup, and API style (REST, GraphQL, gRPC). Read package.json, pyproject.toml, go.mod, or equivalent to understand dependencies.
Step 1: Read the Codebase
Read the route definitions, middleware, models, and tests:
- Route/controller files — all endpoint definitions
- Middleware stack — auth, logging, error handling, rate limiting
- Models/schemas — database models, request/response schemas
- Test files — existing test coverage
Step 2: Check REST Conventions
For each endpoint, verify:
- Correct HTTP methods (GET for reads, POST for creates, PUT/PATCH for updates, DELETE for deletes)
- Plural noun resource paths (
/users, not/getUser) - Proper status codes (201 for created, 204 for no content, 404 for not found, not 200 for everything)
- Consistent response envelope or format
- Idempotent operations where expected (PUT, DELETE)
- No verbs in URLs (
/users/123, not/getUser/123)
Step 3: Check Auth on All Endpoints
Verify:
- Every endpoint has auth middleware (or is explicitly marked as public with justification)
- Auth checks happen before business logic, not after
- Authorization (permissions) is checked, not just authentication (identity)
- Token validation is not hand-rolled when a library exists
- No sensitive data in URLs or query parameters
Step 4: Check Input Validation
Verify:
- All request bodies are validated against a schema
- Path parameters and query parameters are validated (type, range, format)
- Validation happens at the boundary (controller/route level), not deep in business logic
- Validation errors return 400 with specific field-level error messages
- No raw user input reaches database queries (SQL injection prevention)
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.
- 17d ago First seen · 138 lines · 52 tokens per session scan A c65e9721ed79
spine-review is a skill published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 9d ago), licensed MIT. It adds 52 tokens to every session and 1,303 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-09-27.
Other skills, from other repositories
engineer
Software engineer specialist (IRC handle @dev) dispatched to write and test application code, database schema migrations, and infrastructure configuration files.
API Compatibility and Test Gap Review
Detect breaking API contract changes, DTO modifications without compatibility handling, and missing tests for changed API boundaries.
bullmq-jobs
Skill "bullmq-jobs" from lukasrepublic/agentic-foundry, covering when to trigger, procedure, inputs, outputs and quality bar.
API Versioning & Backward Compatibility
Ensure API/contract changes specify versioning strategy, backward compatibility, deprecation plan, and migration guidance.
Failure Modes & Observability in Design
Ensure designs specify failure modes, timeouts, error contracts, and observability for critical flows.
Service Integration & Contracts
Ensure cross-service integration defines contracts, ownership, failure handling, versioning, and rollout/rollback expectations.