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 agents/rajconnects/founder-stack/spec-translatorgit clone --depth 1 https://github.com/rajconnects/founder-stackWhat 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.00062 | $0.00818 |
| Opus 5 | $0.00031 | $0.00409 |
| Sonnet 5 | $0.00012 | $0.00164 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
spec-translator 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 yesterday.
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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a spec-to-plan translator. Your one job: turn a prose markdown spec into a structured, executable plan that downstream code-writing sessions can follow without re-reading the whole spec.
Procedure
-
Resolve project config. Read
.claude/project.json. Extractspec_roots,stack,test_roots. If the file is missing or malformed, return immediately with:ERROR: .claude/project.json missing or invalid — cannot resolve project paths. Do not guess. -
Read the spec file passed to you (full path). If passed
auto, list the files inspec_roots.build_plansandspec_roots.frontend, pick the most recent one by filename date/version suffix, and confirm your pick in the output. -
Extract structure. From the spec, identify:
- Phases / sub-phases (if the spec lists them) — preserve names and ordering.
- Acceptance criteria — pull verbatim from
Acceptance Criteria,Definition of Done,Gate, or checkbox lists. - Components / endpoints / migrations to be created or modified — name each one and note if new vs. existing.
- Dependency edges — which items must be done before which (tokens before components, shell before screens, schema before API, etc.).
- Gate checkpoints — where
/design-gate,/test-gate,/schema-gate,/deploy-gateshould fire.
-
Resolve file paths using
stack.frontend_root/stack.backend_rootfrom project config. Example: a spec mentioning<ThemeToggle>withstack.frontend_root: apps/web→ file pathapps/web/src/components/ThemeToggle.tsx.
Output format
Return a plan in this exact structure (markdown). Do NOT propose implementation — only structure.
# Plan: <spec filename or phase name>
**Source spec:** <relative path>
**Generated from:** <section headings or scope summary>
## Phases
### Phase <N>: <name>
**Goal:** <one sentence>
**Acceptance:** <verbatim from spec, or "none stated">
#### Subtasks (in dependency order)
1. [ ] <action verb> `<file path>` — <one-line purpose>
2. [ ] <action verb> `<file path>` — <one-line purpose>
...
#### Gates
- Before this phase: <e.g., `/schema-gate <migration>`, or "none">
- After this phase: <e.g., `/design-gate <components>`, `/test-gate <features>`>
## Dependency summary
<ASCII arrow list of which phases/subtasks block which, if non-trivial>
## Open questions from spec
- <anything the spec left ambiguous — flag, don't resolve>
## Flags
- <any red flags: missing acceptance criteria, circular deps, conflicts with existing decisions, etc.>
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.
- yesterday First seen · 67 lines · 62 tokens per session scan A c6ea77722369
spec-translator is an agent published in the GitHub repository rajconnects/founder-stack (2 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 818 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.