Borrowing it
Nothing to install: this file belongs to girishr/SpecPilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/girishr/SpecPilot/main/.claude/skills/specpilot-project/SKILL.mdgit clone --depth 1 https://github.com/girishr/SpecPilotWrote 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/girishr/specpilot/specpilot-project)<a href="https://agentmods.dev/skills/girishr/specpilot/specpilot-project"><img src="https://agentmods.dev/badge/skills/girishr/specpilot/specpilot-project/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/girishr/specpilot/specpilot-project"><img src="https://agentmods.dev/badge/skills/girishr/specpilot/specpilot-project.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.00028 | $0.00677 |
| Opus 5.5 | $0.00011 | $0.00271 |
| Sonnet 5.5 | $0.00006 | $0.00135 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
specpilot-project 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 2mo 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpecPilot Project Context
This Skill provides context about the SpecPilot SDD CLI project structure, specifications, and development practices.
Quick Start
The project uses Specification-Driven Development (SDD). All context lives in the .specs/ folder:
- .specs/project/ - Project metadata and requirements
- .specs/architecture/ - System design and API specifications
- .specs/planning/ - Tasks, roadmap, and project management
- .specs/quality/ - Testing strategies and quality guidelines
- .specs/development/ - AI prompts, context, and development logs
Key Files to Reference
- .specs/project/project.yaml - Project configuration, rules, and tech stack
- .specs/project/requirements.md - Functional and non-functional requirements
- .specs/architecture/architecture.md - System architecture and design decisions
- .specs/planning/tasks.md - Current tasks, sprints, and priorities
- .specs/development/prompts.md - AI interaction history and onboarding guide
Project Rules
- Update .specs/ files when making changes
- Maintain .specs/ as single source of truth
- Never modify .specs/ folder structure or file names
- Document decisions in context.md
- Update prompts.md with AI interactions
- Follow stable ID conventions (REQ-###, TASK-###, ARCH-###)
Architecture Overview
- Project: SpecPilot SDD CLI
- Language: TypeScript
- Framework: Node.js / Commander.js
- Key modules:
specFileGenerator,ideConfigGenerator,agentConfigGenerator,specBackfiller,specArchiver,specValidator
Development Process
- Review requirements in .specs/project/requirements.md
- Check tasks in .specs/planning/tasks.md
- Reference architecture in .specs/architecture/architecture.md
- Update specs after major changes
- Document decisions and context
AI Onboarding
For full AI onboarding instructions, see .specs/development/prompts.md.
Code Philosophy — Write Only What Needed
- Need exist? No → skip. Say why.
- Already in codebase? → reuse. Not rewrite.
- Stdlib do it? → use it.
- Native or installed dep cover it? → use. No new deps.
- One line do it? → write that.
- Only then: minimum code that work.
- Never cut: validation, error handling, security, explicit requirement.
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.
- 2mo ago First seen · 75 lines · 28 tokens per session scan A 74d2d1e8948d
specpilot-project is a skill published in the GitHub repository girishr/SpecPilot (39 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 677 once invoked, about $0.0001 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 skills, from other repositories
cli-forge-demo
Generate a reproducible live-demo kit for any project: a staged demo script (DEMO.md), deterministic seed and idempotent reset wired into the project's own task runner (make / just / task / npm / ansible / flux / chainsaw — never an imposed .sh), a pre-flight checklist, and a backup recording. Picks the best delivery…
gws-calendar
Google Calendar: Manage calendars and events.
gws-gmail-send
Skill "gws-gmail-send" from googleworkspace/cli, covering gmail +send, usage, flags, examples and tips.
gws-gmail-watch
Gmail: Watch for new emails and stream them as NDJSON.
gws-gmail
Gmail: Send, read, and manage email.
obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.