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 commands/hundia/autospec/create-specgit clone --depth 1 https://github.com/Hundia/autospecWhat 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.00000 | $0.01401 |
| Opus 5 | $0.00000 | $0.00700 |
| Sonnet 5 | $0.00000 | $0.00280 |
| Haiku 4.5 | $0.00000 | $0.00140 |
Grade A, and why
create-spec 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 2d 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Spec
Generate a new feature specification following the Spec-Driven Development template.
Usage
/create-spec [feature_name]
Example: /create-spec notifications
Instructions
When this command is invoked:
-
Gather requirements from the user:
- Ask clarifying questions about the feature
- Understand the problem being solved
- Identify constraints and dependencies
-
Read existing specs for context:
specs/01_product_manager.md- Product vision and principlesspecs/02_backend_lead.md- Backend patternsspecs/03_frontend_lead.md- Frontend patternsspecs/04_db_architect.md- Database conventions
-
Determine spec number:
- Check existing specs in
specs/folder - Use next available number (e.g., 10, 11, etc.)
- Feature specs start at 10+
- Check existing specs in
-
Generate spec document with these sections:
# SPEC: [Feature Name]
**Version:** 1.0
**Created:** [Date]
**Status:** Draft
---
## 1. Vision
### Problem Statement
What problem does this solve?
### Success State
What does success look like?
### Who Benefits
Which users benefit from this feature?
---
## 2. Requirements
### Functional Requirements
| ID | Requirement | Priority | Notes |
|----|-------------|----------|-------|
| FR-1 | [Requirement] | Must Have | |
| FR-2 | [Requirement] | Should Have | |
| FR-3 | [Requirement] | Nice to Have | |
### Non-Functional Requirements
| ID | Requirement | Metric |
|----|-------------|--------|
| NFR-1 | Performance | [Target] |
| NFR-2 | Security | [Standard] |
| NFR-3 | Scalability | [Target] |
---
## 3. Database Schema (if applicable)
```sql
-- New tables or alterations
CREATE TABLE feature_table (
id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
-- columns
created_at TIMESTAMPTZ DEFAULT NOW(),
updated_at TIMESTAMPTZ DEFAULT NOW()
);
CREATE INDEX idx_feature_table_... ON feature_table(...);
4. API Endpoints (if applicable)
| Method | Endpoint | Description | Auth |
|---|---|---|---|
| GET | /api/v1/... | Get items | Yes |
| POST | /api/v1/... | Create item | Yes |
Request/Response Examples
GET /api/v1/feature
// Response
{
"data": [],
"meta": {
"total": 0,
"page": 1
}
}
POST /api/v1/feature
// Request
{
"field": "value"
}
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.
- 2d ago First seen · 263 lines · 0 tokens per session scan A 5217b8e99bbb
create-spec is a command published in the GitHub repository Hundia/autospec (4 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,401 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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.