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/jsegov/shipspec-claude-code-plugin/agent-promptsnpx skills add jsegov/shipspec-claude-code-plugin --skill agent-promptsgit clone --depth 1 https://github.com/jsegov/shipspec-claude-code-pluginWrote 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/jsegov/shipspec-claude-code-plugin/agent-prompts)<a href="https://agentmods.dev/skills/jsegov/shipspec-claude-code-plugin/agent-prompts"><img src="https://agentmods.dev/badge/skills/jsegov/shipspec-claude-code-plugin/agent-prompts.svg" alt="Measured on agentmods" 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.00059 | $0.01984 |
| Opus 5 | $0.00030 | $0.00992 |
| Sonnet 5 | $0.00012 | $0.00397 |
| Haiku 4.5 | $0.00006 | $0.00198 |
Grade A, and why
agent-prompts 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 5d 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Prompt Generation
Create structured task prompts that coding agents can execute effectively.
Output Files
Task generation produces two files:
| File | Purpose | Used By |
|---|---|---|
TASKS.json |
Machine-parseable metadata | Plugin agents, hooks, commands |
TASKS.md |
Human-readable task prompts | Developers, code review |
Source of Truth: TASKS.json is authoritative. TASKS.md is a derived human-readable view.
TASKS.json Structure
{
"version": "1.0",
"feature": "feature-name",
"summary": {
"total_tasks": 5,
"total_points": 18,
"critical_path": ["TASK-001", "TASK-003", "TASK-005"]
},
"phases": [
{ "id": 1, "name": "Foundation" },
{ "id": 2, "name": "Core Implementation" },
{ "id": 3, "name": "Polish" }
],
"tasks": {
"TASK-001": {
"title": "Setup Database Schema",
"status": "not_started",
"phase": 1,
"points": 3,
"depends_on": [],
"blocks": ["TASK-002", "TASK-003"],
"prd_refs": ["REQ-001", "REQ-002"],
"sdd_refs": ["Section 5.1"],
"acceptance_criteria": [
"Schema file exists at db/schema.sql",
"All tables have primary keys",
"Foreign key relationships match SDD",
"Migration runs without errors"
],
"testing": [
"Run migration: npm run db:migrate",
"Verify tables: npm run db:verify"
],
"prompt": "## Context\nThis task establishes the data layer...\n\n## Requirements\n- Create users table with id, email, created_at\n..."
}
}
}
Task Fields
| Field | Type | Description |
|---|---|---|
title |
string | Clear, action-oriented task title |
status |
enum | "not_started" | "in_progress" | "completed" |
phase |
integer | Phase number (1-indexed) |
points |
integer | Fibonacci story points: 1, 2, 3, 5, 8 |
depends_on |
array | Task IDs that must complete first |
blocks |
array | Task IDs that depend on this task |
prd_refs |
array | Requirement IDs (REQ-XXX) this task addresses |
sdd_refs |
array | SDD section references |
acceptance_criteria |
array | Verifiable criteria for completion |
testing |
array | Test commands or verification steps |
prompt |
string | Full markdown prompt for implementation |
What ships with it
2 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.
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.
- 5d ago First seen · 269 lines · 59 tokens per session scan A 90ad1e85dc20
agent-prompts is a skill published in the GitHub repository jsegov/shipspec-claude-code-plugin (20 stars, last pushed 7mo ago), licensed MIT. It adds 59 tokens to every session and 1,984 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
gsd-plan-review-convergence
Cross-AI plan convergence - replan until review concerns are resolved.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
gsd-ns-manage
Route to the appropriate management skill based on the user's intent. gsd-config (settings + advanced + integrations + profile) and gsd-workspace (new + list + remove) are post-#2790 consolidated entries.
gsd-validate-phase
Retroactively audit and fill Nyquist validation gaps for a completed phase.
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
spec-kitty-spdd-reasons
Drive REASONS Canvas authoring and review for Spec Kitty missions that opted in to Structured-Prompt-Driven Development (SPDD) via charter selection. Triggers: "use SPDD", "use REASONS", "generate a REASONS canvas", "apply structured prompt driven development", "make this mission SPDD". Does NOT handle: enforcing SPDD…