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 dayvisonassis/sdd-skills --skill gate-buildergit clone --depth 1 https://github.com/dayvisonassis/sdd-skillsWrote 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/dayvisonassis/sdd-skills/gate-builder)<a href="https://agentmods.dev/skills/dayvisonassis/sdd-skills/gate-builder"><img src="https://agentmods.dev/badge/skills/dayvisonassis/sdd-skills/gate-builder/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/dayvisonassis/sdd-skills/gate-builder"><img src="https://agentmods.dev/badge/skills/dayvisonassis/sdd-skills/gate-builder.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00099 | $0.07761 |
| Opus 5.5 | $0.00040 | $0.03104 |
| Sonnet 5.5 | $0.00020 | $0.01552 |
| Haiku 4.5 | $0.00010 | $0.00776 |
Grade A, and why
gate-builder 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 16d 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 — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gate Builder
Construct the deterministic quality gates of a project — the automated, pass/fail checks that guard structural and behavioral integrity (see https://github.com/dayvisonassis/sdd-skills/blob/main/docs/Como_criar_gates.md). The skill reads the analysis reports, decides which gates the project needs, proposes a plan, and — after confirmation — writes the gate configs/scripts and a single orchestration entry point (runGate), verifying each gate actually runs.
Where this fits the SDD flow:
gate-builderbuilds the gate infrastructure that must exist before features are spec'd. Later,spec-writerdeclares these gates (byid) in each feature'scontract.md, andimplement-feature/evaluatorexecute them. Seehttps://github.com/dayvisonassis/sdd-skills/blob/main/docs/ARQUITETURA_DAS_SKILLS.mdandhttps://github.com/dayvisonassis/sdd-skills/blob/main/docs/Como_criar_gates.md.
INPUT
Free-form. The skill needs:
- Deep Analysis Report (primary source) — produced by the
deep-analyzeragent. Provides cross-cutting patterns, anti-patterns, test gaps, config-access patterns (e.g. scatteredprocess.env), and complexity. - Architecture Analysis Report (secondary source) — produced by the
architecture-analyzeragent. Provides the stack/runtime/framework, dependency inventory, and the test infrastructure/tooling. - Auto-discovery: if paths are not passed, look in
docs/architecture/for the most recentdeep-analysis-*.md(primary) andarchitecture-analysis-*.md(secondary). - Optional free-form overrides — e.g. "lint only", "no dead-code gate", "strict zero-warnings now", "don't touch package.json".
If neither report is found, the skill can still operate in a reduced mode by reading the codebase directly (see Edge Cases), but the reports are strongly preferred — request them if the codebase is large/ambiguous.
OUTPUT
- Phase 1 — a Gate Plan (chat + saved doc): which gates, which commands/configs, greenfield vs. brownfield strategy, and the
runGateorder. Each gate gets a stableid(typecheck,lint,build,tests,arch,deadcode, ...) — the sameidspec-writer will use incontract.md. - Phase 2 — after confirmation — the gate infrastructure: config files, scripts,
package.json(or equivalent) entries, and therunGateorchestrator, plus a shortGATES.mddocumenting how to run them. - A verification report: each gate executed once, with pass/fail and notes (especially the brownfield baseline of pre-existing warnings/failures).
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.
- 16d ago Changed · +2 lines d8a439a663c9
- 18d ago Changed · +24 lines 3ba63afb534f
- 25d ago Changed 75865f55c309
- 1mo ago Changed · +25 lines b0d67cec6c38
- 2mo ago First seen · 249 lines · 99 tokens per session scan A f1dcf87cee87
gate-builder is a skill published in the GitHub repository dayvisonassis/sdd-skills (3 stars, last pushed 16d ago), licensed MIT. It adds 99 tokens to every session and 7,761 once invoked, about $0.0004 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-31.
Other skills, from other repositories
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
critique
Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.
ship
Pre-release gate. Run the full gate, responsive + render checks, then produce the release checklist (README badge/current/changelog). Use before tagging a release.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
ai-eval-plan
Design an evaluation plan for an LLM or AI feature before shipping it. Use when asked how to evaluate a prompt/model/agent, set up an eval harness, define quality metrics for an AI feature, or build a regression gate. Produces an eval plan — task definition, datasets, metrics & rubrics, baselines, automated + human…
browser-test-loop
Use to actually verify a web change in a real browser instead of assuming it works — click through a flow, catch console errors, check a form submits, confirm a fix on the page. Trigger when a UI change needs proof, a bug only reproduces in the browser, or the user asks to test, check, or screenshot the running app.