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 avizmarlon/agent-skills --skill adr-spec-gategit clone --depth 1 https://github.com/avizmarlon/agent-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/avizmarlon/agent-skills/adr-spec-gate)<a href="https://agentmods.dev/skills/avizmarlon/agent-skills/adr-spec-gate"><img src="https://agentmods.dev/badge/skills/avizmarlon/agent-skills/adr-spec-gate/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/avizmarlon/agent-skills/adr-spec-gate"><img src="https://agentmods.dev/badge/skills/avizmarlon/agent-skills/adr-spec-gate.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.00049 | $0.01979 |
| Opus 5 | $0.00024 | $0.00989 |
| Sonnet 5 | $0.00010 | $0.00396 |
| Haiku 4.5 | $0.00005 | $0.00198 |
Grade A, and why
adr-spec-gate 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 10d 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADR + Spec Gate — Mandatory Entry Point for Development
Overview
Every new project and every non-trivial feature must pass through a dual-gate entry point before any code is written. This skill enforces the discipline of explicit design documentation before implementation.
The two required artifacts:
- Specification (Spec) — What to build, why, and how.
- Architecture Decision Record (ADR) — Why non-obvious design choices were made.
This gate prevents common failures: discovering broken assumptions mid-build, remaking decisions that were already made weeks earlier, and projects that only "exist" in chat and dissolve when the conversation ends.
1. Specification
A specification is a document that fully describes a feature or system at the design level, sufficient for another engineer (or AI agent) to continue implementation without asking the original author questions.
Minimal Specification Template
# <Feature/System Name> Specification
## Objective
What problem does this solve? (1-2 sentences)
## Scope
What is IN scope?
- Explicit feature list
- Boundaries
What is OUT of scope?
- What will NOT be built now (and why)
## Requirements
- User-visible requirements
- Non-functional requirements (performance, security, scale)
- Constraints (regulatory, technical, business)
## Proposed Architecture
- High-level design
- Key components and interactions
- Data model (if applicable)
- External dependencies
## Inputs and Outputs
- What does the system accept?
- What does it produce?
- Format and validation rules
## Error Handling
- What can fail?
- How should failures be handled?
- Recovery strategy
## Success Metrics
- How will we know this was built correctly?
- Quantifiable measures if possible
Spec Location
- Default:
docs/<feature-name>-spec.mdor a dedicatedSPEC.mdin the root. - For existing features: add a new section to the living spec rather than fragmenting.
Spec Quality Check
- Spec is detailed enough for another engineer to continue without asking questions?
- Scope boundaries are explicit (not just implicit)?
- Non-functional requirements are named (performance, scale, security)?
- Error cases are described, not swept under "error handling TBD"?
- Success metrics are measurable or at least checkable?
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.
- 10d ago First seen · 225 lines · 49 tokens per session scan A f9fd2125f8b9
adr-spec-gate is a skill published in the GitHub repository avizmarlon/agent-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 1,979 once invoked, about $0.0002 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 skills, from other repositories
agent-carnet
Use this skill when the user asks to save, recall, find, or organize notes. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check the notebook', 'find in carnet'. Also use proactively when discovering findings worth preserving across sessions.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
security-audit
Audit a codebase or directory for security issues (hardcoded secrets, injection, unsafe deserialization, weak crypto, authz gaps) and produce a structured findings report. Use when the user asks for a security review, an audit, or to check code for vulnerabilities. Report only — never fix.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
taiyi-evolve
A workflow skill that compares the implemented code with the frozen design after development and testing. It records architecture changes and proposes updates to DESIGN.md, the document describing the intended system structure.
taiyi-diagram-c4
A code-scanning tool that builds C4 architecture documents from a repository. It separates facts observed in the code from conclusions inferred about the design and uses Mermaid diagrams as the source format.