Borrowing it
Nothing to install: this file belongs to s-hiraoku/vscode-sidebar-terminal. 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/s-hiraoku/vscode-sidebar-terminal/main/.claude/commands/openspec/agents-gen.mdgit clone --depth 1 https://github.com/s-hiraoku/vscode-sidebar-terminalWrote 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/s-hiraoku/vscode-sidebar-terminal/agents-gen)<a href="https://agentmods.dev/commands/s-hiraoku/vscode-sidebar-terminal/agents-gen"><img src="https://agentmods.dev/badge/commands/s-hiraoku/vscode-sidebar-terminal/agents-gen/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/s-hiraoku/vscode-sidebar-terminal/agents-gen"><img src="https://agentmods.dev/badge/commands/s-hiraoku/vscode-sidebar-terminal/agents-gen.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.00013 | $0.05108 |
| Opus 5 | $0.00006 | $0.02554 |
| Sonnet 5 | $0.00003 | $0.01022 |
| Haiku 4.5 | $0.00001 | $0.00511 |
Grade B, and why
agents-gen scanned grade B with 1 finding 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 9d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
tools: ["*"] How it starts
The opening of the file, as written. The whole thing — 814 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSpec Agents Generator (Meta-Command)
Analyze OpenSpec change specifications and automatically generate:
- Implementation-specialized agent (
.claude/agents/{change-id}-implementer.md) - Dedicated slash command (
.claude/commands/implement-{change-id}.md)
Both generated artifacts integrate with MCP servers and Skills for optimal implementation efficiency.
Execution Workflow
When this command is invoked (e.g., /openspec:agents-gen fix-terminal-initialization-bugs):
Step 1: Validate OpenSpec Change
Input: {ARGUMENTS} (change-id)
Validation:
# Check if OpenSpec change exists
if [ ! -d "openspec/changes/{ARGUMENTS}" ]; then
echo "❌ Error: OpenSpec change '{ARGUMENTS}' not found"
echo "Available changes:"
ls -1 openspec/changes/
exit 1
fi
# Check required files
required_files=("proposal.md" "tasks.md")
for file in "${required_files[@]}"; do
if [ ! -f "openspec/changes/{ARGUMENTS}/$file" ]; then
echo "❌ Error: Missing required file: $file"
exit 1
fi
done
Output: ✅ Validation passed / ❌ Validation failed with error details
Step 2: Analyze OpenSpec Specification
Files to Read:
openspec/changes/{ARGUMENTS}/proposal.md- Problem statement, solution, scopeopenspec/changes/{ARGUMENTS}/tasks.md- Implementation phases and tasksopenspec/changes/{ARGUMENTS}/specs/**/*.md- Delta specifications (if exists)
Analysis Objectives:
2.1 Extract Technical Domain
Determine primary technical areas affected:
- Terminal Lifecycle Management: Terminal creation, deletion, process states
- WebView Development: Message routing, UI rendering, event handling
- Performance Optimization: Rendering, memory, buffering
- Testing: Unit tests, integration tests, E2E tests (Playwright)
- Configuration Management: Settings, profiles, feature toggles
- Session Persistence: Scrollback save/restore, state serialization
- AI Agent Detection: Pattern matching, visual indicators
- Error Handling: Race conditions, memory leaks, validation
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.
- 9d ago First seen · 814 lines · 13 tokens per session scan B b0eb969d3238
agents-gen is a command published in the GitHub repository s-hiraoku/vscode-sidebar-terminal (21 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 5,108 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.