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 skills add techygarg/lattice --skill requirement-forge-refinergit 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-refiner)<a href="https://agentmods.dev/skills/techygarg/lattice/requirement-forge-refiner"><img src="https://agentmods.dev/badge/skills/techygarg/lattice/requirement-forge-refiner/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/skills/techygarg/lattice/requirement-forge-refiner"><img src="https://agentmods.dev/badge/skills/techygarg/lattice/requirement-forge-refiner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00121 | $0.02635 |
| Opus 5.5 | $0.00048 | $0.01054 |
| Sonnet 5.5 | $0.00024 | $0.00527 |
| Haiku 4.5 | $0.00012 | $0.00264 |
Grade A, and why
requirement-forge-refiner 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 1mo 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirement Forge Refiner
What This Produces
- Output:
.lattice/standards/requirement-standards.md(or custom path from.lattice/config.yaml→paths.requirement_standards) - Two modes:
- Overlay (
mode: overlay): A slim document containing only sections that differ from the built-in defaults. Therequirement-qualityatom reads its embeddeddefaults.mdfirst, then applies this document's sections on top. This is the expected common case. - Override (
mode: override): A comprehensive standalone document that fully replaces the atom's embedded defaults. For teams whose product process differs fundamentally from the defaults.
- Overlay (
- Default mode: Overlay — produces only what the team wants to change
- Config key:
paths.requirement_standardsin.lattice/config.yaml - Consumed by:
requirement-qualityatom (via config resolution) →requirement-forgemolecule (composes the atom) - Template: Read
./assets/template.mdfor the full document structure, default content, and interview guidance comments
Scope Clarification
This refiner defines how requirements are structured and expressed for this project. It does not define:
- What to build (that is the requirement-forge molecule's job)
- Architecture or technical design (that is the architecture-refiner's job)
- Domain modeling patterns (that is the ddd-refiner's job)
The standards produced here answer: what is an epic, what is a feature, what is a scenario, how are ACs written, how are features named and prioritized. These are the rules the requirement-quality atom enforces — the molecule composes the atom and inherits those rules automatically.
Before You Begin
Check for an existing standards document
- Read
.lattice/config.yaml— checkpaths.requirement_standards. - If the path exists, read that file. Ask the user:
- "You already have a requirement standards document. Would you like to revise it (update specific sections), start fresh (new interview), or add to it (add new sections)?"
- Revise: load the existing document, walk through only the sections the user wants to change, update in place.
- Start fresh: proceed with the full interview flow below.
- Add to it: skip to the "New Sections" part of the interview.
- If no config or no existing document, proceed with the full interview.
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.
- 1mo ago First seen · 215 lines · 121 tokens per session scan A 75302dbf154b
requirement-forge-refiner is a skill published in the GitHub repository techygarg/lattice (209 stars, last pushed yesterday), licensed MIT. It adds 121 tokens to every session and 2,635 once invoked, about $0.0005 per session on Opus 5.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
gaia-triage
Triage the Gaia issue backlog and skill-batch intake queue. Use this skill when someone asks to: "triage issues", "clean up the issue tracker", "review the backlog", "close stale issues", "process the intake queue", "review skill-batches", "evaluate draft skill proposals", "approve or reject pending skills", "is this…
wayfinder
Chart a too-big effort as a shared map of decision tickets on the Gaia headquarters issue tracker, then resolve them one at a time until the way to the destination is clear. Use when someone says: "this is too big for one session", "chart a map", "wayfinder map", "plan this effort", "what do we need to decide first"…
gaia-issue-resolver
End-to-end plan → implement → review pipeline that takes one triaged Gaia issue to a merged-ready PR, with Kill Criteria on the issue and zero follow-up debt. Use when someone says: "resolve this issue", "take #N end-to-end", "work the P0 queue", "fix and ship this issue", "run the resolver", "close out this issue…
chief-information-officer
The CIO's remit — running the technology the company works on, service quality, IT spend, and the boundary with product engineering. Use this to set IT priorities, decide what IT owns versus engineering, structure IT spend or an IT roadmap, judge whether to build, buy or outsource, or work out why IT is seen as a cost…
chief-operating-officer
Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and service delivery. Use this when execution is the problem rather than strategy, to design or fix a process, to resolve cross-functional handoff failures, to plan capacity, to…
chief-product-officer
Owns what gets built and why: product strategy, roadmap, discovery, user experience, and the definition of success for each release. Use this to decide what to build next, to cut scope, to turn a business goal into a product bet, to judge whether a feature is worth its cost, or when engineering and go-to-market…