Borrowing it
Nothing to install: this file belongs to sapientpants/deepsource-mcp-server. 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/sapientpants/deepsource-mcp-server/main/.claude/commands/spec-feature.mdgit clone --depth 1 https://github.com/sapientpants/deepsource-mcp-serverWrote 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/commands/sapientpants/deepsource-mcp-server/spec-feature)<a href="https://agentmods.dev/commands/sapientpants/deepsource-mcp-server/spec-feature"><img src="https://agentmods.dev/badge/commands/sapientpants/deepsource-mcp-server/spec-feature/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/commands/sapientpants/deepsource-mcp-server/spec-feature"><img src="https://agentmods.dev/badge/commands/sapientpants/deepsource-mcp-server/spec-feature.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.00000 | $0.00959 |
| Opus 5.5 | $0.00000 | $0.00384 |
| Sonnet 5.5 | $0.00000 | $0.00192 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
spec-feature 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec a Feature
You are about to create a feature specification in Gherkin format and turn it into a GitHub issue ready for implementation.
Process
-
Gather Requirements
- Ask the user for the feature name and description if not provided
- Understand the business value and user needs
- Identify scope, non-goals, and risks
-
Write Gherkin Specification Create a comprehensive specification including:
- Feature name and description
- Background (if needed)
- Scenarios using Given/When/Then format
- Examples with data tables where appropriate
- Acceptance Criteria
- Non-Goals (what this feature won't do)
- Risks & Mitigations
- Technical Considerations
-
Format as GitHub Issue Structure the issue with:
- Clear title:
feat: [Feature Name] - Labels:
enhancement,needs-implementation - Milestone (if applicable)
- Complete Gherkin specification in the body
- Testing requirements
- Clear title:
-
Create the Issue Use the
ghCLI to create the issue:gh issue create --title "feat: [Feature Name]" \ --body "[Full specification]" \ --label enhancement \ --label needs-implementation
Template for Issue Body
## Feature: [Feature Name]
### Business Value
[Describe the business value and user benefit]
### User Story
As a [type of user]
I want [goal/desire]
So that [benefit/value]
### Gherkin Specification
```gherkin
Feature: [Feature Name]
[Feature description explaining the feature's purpose]
Background:
Given [common preconditions for all scenarios]
Scenario: [Happy path scenario]
Given [initial context]
When [action/event]
Then [expected outcome]
And [additional outcomes]
Scenario: [Edge case or error scenario]
Given [initial context]
When [action/event]
Then [expected outcome]
Scenario Outline: [Parameterized scenario if needed]
Given [context with <parameter>]
When [action with <parameter>]
Then [outcome with <expected>]
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 · 160 lines · 0 tokens per session scan A 308a4dd60905
spec-feature is a command published in the GitHub repository sapientpants/deepsource-mcp-server (7 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 959 tokens. 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-31.
spec-feature compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| spec-featuresapientpants/deepsource-mcp-server | Command | 7 | 1y ago | MIT | A | 0 | Claude Code |
| compileAURORA-NEURO/aurora-agent | Command | 1 | 10d ago | Apache-2.0 | A | 25 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |