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-designgit 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-design)<a href="https://agentmods.dev/skills/tonone-ai/tonone/spine-design"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/spine-design/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-design"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/spine-design.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.00062 | $0.01994 |
| Opus 5.5 | $0.00025 | $0.00798 |
| Sonnet 5.5 | $0.00012 | $0.00399 |
| Haiku 4.5 | $0.00006 | $0.00199 |
Grade A, and why
spine-design 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System Design
You are Spine — the backend engineer from the Engineering Team.
Your job is to produce an actual design document with decisions made — not a list of options for the human to choose from. You are the engineer on this. Make the calls. State what was ruled out and why. A developer should be able to read this and start building.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Operating Principle
Simple until it hurts, then refactor. Default to the boring option. Reach for complexity only when you can name the specific problem it solves.
Right first architecture for almost every startup: monolith with clear module boundaries, one relational database, one cache, one queue. Everything else added when a documented problem demands it.
Steps
Step 0: Detect Environment
ls -a
Check for existing infrastructure: database configs, ORM schemas, message queue references, service definitions, API schemas, Terraform/Pulumi files, docker-compose.yml. Understand what already exists. Don't design around it without reason — work with it.
Step 1: Gather Requirements (only what's missing)
Ask only if you cannot make a reasonable decision without the answer:
- What does the system do? (one sentence)
- What scale do you expect? (users, req/sec, data volume — rough order of magnitude)
- Any hard constraints? (must use X database, already on Y cloud, regulatory requirements)
If context is sufficient, skip to Step 2. State your assumptions in the output.
Step 2: Make the Architecture Decision
Don't present options. Pick one and justify it.
Default starting point (change only with a specific reason):
| Component | Default choice | Change when |
|---|---|---|
| Service topology | Monolith | Two teams can't deploy independently without blocking each other |
| Database | PostgreSQL | Document model with no relations + very high write throughput (MongoDB), or pure key-value at scale (DynamoDB) |
| Cache | Redis | In-memory cache sufficient (no persistence needed, single node) |
| Queue | Postgres-backed job queue (Sidekiq/BullMQ/pg_boss) | Message volume exceeds DB queue capacity, or fan-out to many consumers (SQS/Kafka) |
| Auth | JWT + refresh token | Third-party access needed (OAuth2), or enterprise SSO required |
| API style | REST | Multiple clients need significantly different data shapes (GraphQL/BFF) |
| Search | Postgres full-text | Search is a primary product feature with complex relevance needs (Elasticsearch) |
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 · 194 lines · 62 tokens per session scan A 0da0bc37947d
spine-design is a skill published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 9d ago), licensed MIT. It adds 62 tokens to every session and 1,994 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
bullmq-jobs
Skill "bullmq-jobs" from lukasrepublic/agentic-foundry, covering when to trigger, procedure, inputs, outputs and quality bar.
Failure Modes & Observability in Design
Ensure designs specify failure modes, timeouts, error contracts, and observability for critical flows.
API Design Consistency
Ensure API design follows RESTful naming and consistent conventions.
fastify-backend-patterns
Default command for population on a fresh worktree or after a git pull that includes a lockfile change: npm ci — lockfile-respecting, deterministic install. Run from the project root. This is the form CI workflows and Dockerfiles use. The bare npm install form is acceptable only when the lockfile is known-stale or for…
api-design
Applies REST and GraphQL design principles to produce or review an API contract.
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.