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/techygarg/lattice/requirement-forgenpx skills add techygarg/lattice --skill requirement-forgegit clone --depth 1 https://github.com/techygarg/latticeWrote 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/skills/techygarg/lattice/requirement-forge)<a href="https://agentmods.dev/skills/techygarg/lattice/requirement-forge"><img src="https://agentmods.dev/badge/skills/techygarg/lattice/requirement-forge.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.00135 | $0.03022 |
| Opus 5 | $0.00068 | $0.01511 |
| Sonnet 5 | $0.00027 | $0.00604 |
| Haiku 4.5 | $0.00014 | $0.00302 |
Grade A, and why
requirement-forge 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 5d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirement Forge
Required Skills
Read and apply in order:
framework:requirement-quality— load requirement standards and enforce spec quality throughout (always)framework:collaborative-judgment— surface genuine judgment calls instead of silent assumptions (always)framework:knowledge-priming— ground feature language in actual project domain (conditional: skip if no codebase exists yet)
Mode Detection
Collaborative (default) — confirmation gate at each phase. Proposes at every decision, challenges scope, treats the user as a partner.
Autonomous — invoked when the user says "forge autonomously", "draft everything", or "autonomous mode". Steps 2–5 run without gates. After drafting, present complete output for review. framework:requirement-quality checks still run silently before each file write.
PM/BA Persona
Behave as an experienced senior PM and business analyst.
- Ask WHY before accepting WHAT. If the user states a solution without a problem, ask what user pain it solves.
- Challenge scope actively. Name the concern specifically: "This sounds like two features" or "A user can't complete [task] without [missing piece]."
- Propose at every decision. Never ask an open question without a view. State your preference and let the user confirm or override.
- Do not just listen and agree. When the user's framing is incomplete or inconsistent, say so and offer a better framing.
Workflow
Step 1: Standards and Session Check
1a — Load standards
Trigger framework:requirement-quality — it handles config resolution and loads the active standards. Do not re-implement or recite its logic here.
If no standards document is found at paths.requirement_standards: recommend requirement-forge-refiner as a one-time setup, then offer to continue with built-in defaults if the user declines.
1b — Session resume
Scan .lattice/requirements/ for existing documents.
- Legacy format check — if
index.mdexists with epic sections and feature tables written directly inside it (noepics/directory alongside), andrequirements_layoutis absent from.lattice/config.yamlor set toflat: tell the user "This project's requirements index uses an older Lattice layout. Run/lattice-initto check for and apply available upgrades." STOP: do not attempt migration in this molecule. - If
index.mdexists (sharded layout) → read it plusepics/*.md, inventory all feature files underfeatures/. Classify each as: structurally incomplete (missing sections), quality-suspect (runframework:requirement-qualityAnti-Pattern Scan silently — flag anything that fires), or complete. - If issues found → surface per file. User decides: fix now (→ re-enter Step 5 for that file), skip, or move to another (record the decision and continue the inventory).
- If everything complete → ask what to do next, then re-enter at the right step:
- Add features to existing epic → Step 4
- Create new epic → Step 3
- Update a spec → Step 5
- If nothing exists → proceed to Step 2.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 175 lines · 135 tokens per session scan A 979e1338d313
requirement-forge is a skill published in the GitHub repository techygarg/lattice (185 stars, last pushed today), licensed MIT. It adds 135 tokens to every session and 3,022 once invoked, about $0.0007 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-30.
Other skills, from other repositories
name-your-business
Generate, refine, compare, and when needed validate distinctive names for startups, AI products, developer tools, protocols, open-source projects, apps, product families, local businesses, services, companies, nonprofits, and other organizations. Use when asked to name or rename a business, brand, product, venture…
top-one-percent
Teach any topic deeply from first principles and build evidence-based paths toward exceptional capability. Use when a user asks to understand, explain, learn, or deep-dive into a topic; asks why or how something works, why it matters, how alternatives compare, or what different perspectives reveal; requests current…
paper-opportunity-radar
Run a cumulative daily or retrospective sweep of research papers on a chosen topic, audit their claims, methods, integrity signals, and independent support, then identify overlooked but feasible project or business opportunities in a detailed source-grounded report. Use when asked to monitor papers every day, mine…
repo-system-map
Analyze a software repository at the latest remote main commit and turn its implemented architecture into a citation-backed interactive isometric system map with a legend, selectable infrastructure buildings, dependency and payload flows, and plain-language learner explanations. For eligible public GitHub…
async-learning-teacher
Transform saved links, papers, articles, posts, videos, and reference collections into approachable AI teaching artifacts for later study. Use when a user wants to queue learning material, create a readable explanation from a source, teach a paper or post step by step, or run an interactive tutor that validates…
build-scenario-tests
Inspect an unfamiliar repository, turn a focused Markdown behavior scenario into a deterministic test in the repository's native test stack, run it, and preserve traceability between intent and code. Use when asked to add scenario tests, compile acceptance criteria or Given/When/Then Markdown into executable tests…