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 skills/tercel/spec-forge/ideanpx skills add tercel/spec-forge --skill ideagit clone --depth 1 https://github.com/tercel/spec-forgeWhat 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.00100 | $0.05791 |
| Opus 5 | $0.00050 | $0.02896 |
| Sonnet 5 | $0.00020 | $0.01158 |
| Haiku 4.5 | $0.00010 | $0.00579 |
Grade A, and why
idea 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 — 610 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Idea — Brainstorming & Demand Validation
Explore, research, validate, and crystallize ideas through iterative sessions before committing to formal specification. Every idea must prove it's a real need before graduating.
Core Principles
- Brainstorm freely, validate ruthlessly: Early sessions are open and creative; later sessions demand evidence
- Non-linear: Ideas evolve through multiple sessions, not in one sitting
- Research-driven: Use web search, competitive analysis, and user evidence to ground ideas in reality
- Anti-pseudo-requirement: Before graduating, every idea must answer "What happens if we don't build this?" — if the answer is "nothing significant", the idea is not ready
- Persistent: Every session is recorded, nothing is lost
- Project-local: Ideas live in the project's
ideas/directory, close to the codebase and docs they relate to
Storage Structure
ideas/is a top-level directory at the project root, separate fromdocs/. Never nest it insidedocs/.
{project-root}/
├── ideas/ # Brainstorming workspace (TOP-LEVEL, not under docs/)
│ ├── {idea-name}/
│ │ ├── state.json # Status, metadata, and validation checklist
│ │ ├── sessions/
│ │ │ ├── overview.md # Session index: chronological order, summaries
│ │ │ ├── explore-initial-spark.md # First session
│ │ │ ├── research-competitors.md # Second session
│ │ │ ├── validate-demand.md # Third session
│ │ │ └── ...
│ │ ├── research/
│ │ │ ├── competitors.md # Competitive landscape analysis
│ │ │ └── market-notes.md # Market research, user evidence, data points
│ │ └── draft.md # Evolving summary (auto-updated after each session)
│ └── ...
├── docs/ # Formal spec documents (PRD, SRS, etc.)
└── .gitignore # Add "ideas/" if you want to keep them private
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 · 610 lines · 100 tokens per session scan A 46515b9f2e45
idea is a skill published in the GitHub repository tercel/spec-forge (5 stars, last pushed 1mo ago), licensed MIT. It adds 100 tokens to every session and 5,791 once invoked, about $0.0005 per session on Opus 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-31.
Other skills, from other repositories
ppt-design-skill
Design, generate, review, and revise editable PowerPoint presentations through a rigorous brief-to-PNG workflow using the public pptx-designer Python library.
manager
Sync session work into GitHub issues, or query track status across repos. Write: find/update issue + W-label. Read: "что по ". Triggers: "создай issue", "синкни сессию", "manager". Not day/week plans (daily-tasks).
weekly-retro
Use when the user is closing an ISO week, reviewing planned outcomes against evidence, interviewing work Areas, resolving unfinished commitments, or asking for "ретро", "weekly retro", "week review", or lessons from the week.
art-director
Orchestrate iterative visual style searches with branch prompts, decision graphs, feedback loops, and final direction selection.
html-draft
Use when user wants a standalone HTML diagram in flat engineering blueprint style — architecture diagrams, system flows, technical spec sheets, component maps. Generates one HTML file using Tailwind v4 (browser CDN) for layout and D3 v7 (CDN) for SVG diagrams. User-invoked only — do NOT auto-trigger. Triggers on…
pm-metrics
Делает ревью продуктовых метрик — тренды, аномалии, root causes и рекомендации к действиям. Включает декомпозицию North Star (L1/L2), диагностику retention-кривых, анализ воронки, разбор A/B-экспериментов, проверку соответствия OKR и фреймворк атрибуции аномалий. User-invoked only — do NOT auto-trigger. Triggers on…