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.
git clone --depth 1 https://github.com/ariel-frischer/autospecWrote 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/ariel-frischer/autospec/autospec.specify)<a href="https://agentmods.dev/commands/ariel-frischer/autospec/autospec.specify"><img src="https://agentmods.dev/badge/commands/ariel-frischer/autospec/autospec.specify/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/ariel-frischer/autospec/autospec.specify"><img src="https://agentmods.dev/badge/commands/ariel-frischer/autospec/autospec.specify.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.00009 | $0.02172 |
| Opus 5.5 | $0.00004 | $0.00869 |
| Sonnet 5.5 | $0.00002 | $0.00434 |
| Haiku 4.5 | $0.00001 | $0.00217 |
Grade A, and why
autospec.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 1mo 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Outline
The text the user typed after /autospec.specify in the triggering message is the feature description. Assume you always have it available in this conversation even if $ARGUMENTS appears literally below. Do not ask the user to repeat it unless they provided an empty command.
Given that feature description, do this:
-
Generate a concise short name (2-4 words) for the branch:
- Analyze the feature description and extract the most meaningful keywords
- Create a 2-4 word short name that captures the essence of the feature
- Use action-noun format when possible (e.g., "add-user-auth", "fix-payment-bug")
- Preserve technical terms and acronyms (OAuth2, API, JWT, etc.)
- Keep it concise but descriptive enough to understand the feature at a glance
- Examples:
- "I want to add user authentication" → "user-auth"
- "Implement OAuth2 integration for the API" → "oauth2-api-integration"
- "Create a dashboard for analytics" → "analytics-dashboard"
- "Fix payment processing timeout bug" → "fix-payment-timeout"
-
Create feature branch and directory: Run the Go command with your generated short-name:
autospec new-feature --json --short-name "<short-name>" "$ARGUMENTS"Parse the JSON output for:
BRANCH_NAME: The full branch name (e.g., "008-user-auth")SPEC_FILE: Path to the spec file (ignore - we'll create spec.yaml instead)FEATURE_NUM: The feature numberAUTOSPEC_VERSION: The autospec version (for _meta section)CREATED_DATE: ISO 8601 timestamp (for _meta section)
Set
FEATURE_DIRtospecs/<BRANCH_NAME>/ -
Generate spec.yaml: Create the YAML specification file with this exact structure.
The structure below is the authoritative schema; follow it directly. Optionally run
autospec artifact spec --schemafor field details; if that probe is unavailable or fails in your environment, continue with the structure below and rely on the validation step instead.
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.
- 1mo ago Changed a206da764a92
- 2mo ago First seen · 219 lines · 9 tokens per session scan A d5a79be501a6
autospec.specify is a command published in the GitHub repository ariel-frischer/autospec (147 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 2,172 once invoked, about $0.0000 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 commands, from other repositories
trex.kind.add-field
Add a new field to an existing Kind, updating all layers consistently.
trex.kind.new
Generate a complete CRUD entity (Kind) using the automated generator script.
trex.openapi.generate
Regenerate the Go client code from OpenAPI specifications. Run this after modifying any openapi/.yaml files.
spek-manage-repos
Add a repo to this project through a guided conversation, inspect the registry, and repair a repo's footprint.
spek-implement
Execute an approved Plan to implement the feature.
spek-knowledge
Search, contribute to, or update the project's knowledge base.