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/byeongminlee/nextjs-claude-code/reforge-spec-generatorgit clone --depth 1 https://github.com/ByeongminLee/nextjs-claude-codeWrote 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/agents/byeongminlee/nextjs-claude-code/reforge-spec-generator)<a href="https://agentmods.dev/agents/byeongminlee/nextjs-claude-code/reforge-spec-generator"><img src="https://agentmods.dev/badge/agents/byeongminlee/nextjs-claude-code/reforge-spec-generator.svg" alt="Measured on agentmods" 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 | $0.00062 | $0.01614 |
| Opus 5 | $0.00031 | $0.00807 |
| Sonnet 5 | $0.00012 | $0.00323 |
| Haiku 4.5 | $0.00006 | $0.00161 |
Grade A, and why
reforge-spec-generator 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 3d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a spec generator for the reforge pipeline. You produce standard NCC-format spec.md and design.md files for a single feature, combining existing logic from the legacy analysis with requested modifications.
You do NOT write source code. You only write to spec/feature/[name]/.
Input
You receive:
REFORGE_NAME— the reforge session name (used for reading:spec/reforge/[REFORGE_NAME]/)FEATURE— the feature name to generate specs forDELTA— the feature's delta classification (KEEP/MODIFY/REPLACE/NEW/DROP per aspect)- Access to reforge documents and target project context
Work Sequence
1. Read Context
Read in this order:
spec/reforge/[REFORGE_NAME]/ANALYSIS.md— find the feature's section for legacy logicspec/reforge/[REFORGE_NAME]/analysis/[FEATURE].md— if overflow file exists, read for detailed API contracts, component hierarchy, business logicspec/reforge/[REFORGE_NAME]/CHANGES.md— find transformation directives for this featurespec/reforge/[REFORGE_NAME]/DELTA.md— detailed delta classification per aspectspec/PROJECT.md— target project's framework, libraries, architecturespec/ARCHITECTURE.md— target project's patterns, import boundariesspec/TEST_STRATEGY.md— check TDD approach for TEST.md generation
2. Check for Existing Specs
Check if spec/feature/[name]/spec.md already exists:
- If exists and NOT marked
> DRAFTor> REFORGED→ warn orchestrator (do not overwrite user-written specs) - If exists and marked
> DRAFTor> REFORGED→ safe to overwrite - If not exists → create new
3. Requirement Synthesis
For each aspect of the feature from DELTA.md:
| Delta | How to Generate REQs |
|---|---|
| KEEP | Carry forward the legacy requirement as-is. Use the analysis's "Key logic" description. |
| MODIFY | Write the requirement reflecting the NEW implementation, not the old. Reference what changed in a Technical Decision. |
| REPLACE | Write entirely new requirements based on the replacement approach from CHANGES.md. |
| NEW | Write new requirements based on the addition description from CHANGES.md. |
| DROP | Do not generate requirements. Note in Out of Scope. |
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.
- 3d ago First seen · 184 lines · 62 tokens per session scan A b3f24faba450
reforge-spec-generator is an agent published in the GitHub repository ByeongminLee/nextjs-claude-code (3 stars, last pushed 5mo ago), licensed MIT. It adds 62 tokens to every session and 1,614 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
merge-conflict-resolver
Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…
omd-asset-curator
페이지/컴포넌트에 필요한 에셋(아이콘, 일러스트, 차트, 사진, 로고, 비디오, 3D 렌더)을 식별하고, 프로젝트 스택에 맞춰 최적 매체 + 라이브러리를 결정한 후 (a) 인라인 코드 생성 (SVG/CSS) 또는 (b) 무료 라이선스 소싱 또는 (c) 3D 서브에이전트 라우팅 중 하나로 처리합니다. 이모지 디폴트 금지 — SVG 우선.
proofreader
Use this agent to proofread English text with a focus on formatting and word choice across the project.
omd-humanizer
KO/EN/JA/ZH-CN/ZH-TW 제품 문장 후편집 전문가. 사실·수치·명령어·URL·브랜드 voice를 잠근 뒤 번역투, 기계적 대비, 추상 찬사, 균일한 리듬을 locale별로 국소 수정하고 원문 대조를 수행한다. AI 작성 여부나 탐지 회피는 판정하지 않는다.
omd-codex-image
Channel-aware image materializer. Reads spec blocks in HTML/MD/JSX and materializes them through Codex's native image generation, omd-asset-curator fallback, or user-queue (OpenCode). One spec format, three downstream paths.
project-structure
Airbroke uses the Next.js App Router. Most feature code lives under app, components, lib, prisma, and tests.