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/rsmdt/the-startup/specifynpx skills add rsmdt/the-startup --skill specifygit clone --depth 1 https://github.com/rsmdt/the-startupWhat 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.00057 | $0.01218 |
| Opus 5 | $0.00028 | $0.00609 |
| Sonnet 5 | $0.00011 | $0.00244 |
| Haiku 4.5 | $0.00006 | $0.00122 |
Grade A, and why
specify 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 yesterday.
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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona
Act as an expert requirements gatherer that creates specification documents for one-shot implementation.
Description: $ARGUMENTS
Interface
SpecStatus { requirements: Complete | Incomplete | Skipped solution: Complete | Incomplete | Skipped decomposition: { tier: Direct | Incremental | Factory | None status: Complete | Incomplete | Skipped } readiness: HIGH | MEDIUM | LOW }
State { target = $ARGUMENTS spec: string // resolved spec directory path (from specify-meta) perspectives = [] mode: Standard | Agent Team classification: Direct | Incremental | Factory // from reference/classifier.md status: SpecStatus }
Constraints
Always:
- Delegate research tasks to specialist agents.
- Display all agent responses to user — complete findings, not summaries.
- Use the appropriate skill at the start of each document phase for methodology guidance.
- Only write or edit files within
.start/anddocs/directories. - Run phases sequentially — Requirements, Solution, Decomposition (user can skip phases).
- Wait for user confirmation between each document phase.
- Track decisions in specification README via reference/output-format.md.
- Git integration is optional — offer branch/commit as an option.
Never:
- Write specification content yourself — always delegate to specialist skills.
- Proceed to next document phase without user approval.
- Skip decision logging when user makes non-default choices.
Reference Materials
- Perspectives — Research perspectives, focus mapping, synthesis protocol
- Classifier — Complexity heuristic for routing to Direct, Incremental, or Factory tier
- Output Format — Decision logging guidelines, documentation structure
- Output Example — Concrete example of expected output format
Workflow
1. Initialize
Use the specify-meta skill to create or read the spec directory.
What ships with it
11 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.
- evals/evals.json 4.2 KB
- evals/fixtures/classifier-direct/requirements.md 288 B
- evals/fixtures/classifier-direct/solution.md 176 B
- evals/fixtures/classifier-factory/requirements.md 337 B
- evals/fixtures/classifier-factory/solution.md 383 B
- evals/fixtures/classifier-incremental/requirements.md 458 B
- evals/fixtures/classifier-incremental/solution.md 301 B
- examples/output-example.md 1.4 KB
- reference/classifier.md 4.0 KB
- reference/output-format.md 682 B
- reference/perspectives.md 1.8 KB
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.
- yesterday First seen · 147 lines · 0 tokens per session scan A 5d4bd876ad0a
specify is a skill published in the GitHub repository rsmdt/the-startup (511 stars, last pushed 28d ago), licensed MIT. It adds 57 tokens to every session and 1,218 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
postgres-database-migration
Use this skill for planning, testing, and safely executing PostgreSQL schema migrations — especially when working with production data or shared databases. Trigger when user asks to: Test a schema migration before applying it to production Add, remove, or rename columns safely on a live table Change a column's data…
design-postgis-tables
Comprehensive PostGIS spatial table design reference covering geometry types, coordinate systems, spatial indexing, and performance patterns for location-based applications.
setup-timescaledb-hypertables
Use this skill when creating database schemas or tables for Timescale, TimescaleDB, TigerData, or Tiger Cloud, especially for time-series, IoT, metrics, events, or log data. Use this to improve the performance of any insert-heavy table. Trigger when user asks to: Create or design SQL schemas/tables AND…
migrate-postgres-tables-to-hypertables
Use this skill to migrate identified PostgreSQL tables to Timescale/TimescaleDB hypertables with optimal configuration and validation. Trigger when user asks to: Migrate or convert PostgreSQL tables to hypertables Execute hypertable migration with minimal downtime Plan blue-green migration for large tables Validate…
pgvector-semantic-search
Use this skill for setting up vector similarity search with pgvector for AI/ML embeddings, RAG applications, or semantic search. Trigger when user asks to: Store or search vector embeddings in PostgreSQL Set up semantic search, similarity search, or nearest neighbor search Create HNSW or IVFFlat indexes for vectors…
postgres-hybrid-text-search
Use this skill to implement hybrid search combining BM25 keyword search with semantic vector search using Reciprocal Rank Fusion (RRF). Trigger when user asks to: Combine keyword and semantic search Implement hybrid search or multi-modal retrieval Use BM25/pgtextsearch with pgvector together Implement RRF (Reciprocal…