SkillKit is a package manager for AI coding-agent skills that installs skills from many sources and translates them between the different formats used by coding agents. It helps developers share skills across agents such as Claude Code, Cursor, Copilot, and Codex.
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 rohitg00/skillkit --skill verification-gatesgit clone --depth 1 https://github.com/rohitg00/skillkitWrote 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/rohitg00/skillkit/verification-gates)<a href="https://agentmods.dev/skills/rohitg00/skillkit/verification-gates"><img src="https://agentmods.dev/badge/skills/rohitg00/skillkit/verification-gates/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/rohitg00/skillkit/verification-gates"><img src="https://agentmods.dev/badge/skills/rohitg00/skillkit/verification-gates.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.00094 | $0.01574 |
| Opus 5.5 | $0.00038 | $0.00630 |
| Sonnet 5.5 | $0.00019 | $0.00315 |
| Haiku 4.5 | $0.00009 | $0.00157 |
Grade A, and why
verification-gates 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification Gates
You are implementing verification gates - explicit checkpoints where work is validated before proceeding. This prevents cascading errors and ensures quality at each phase.
Core Principle
Never proceed to the next phase with unverified assumptions from the previous phase.
A verification gate is a deliberate pause to confirm that prerequisites are met before continuing.
Standard Verification Gates
Gate 1: Requirements Verification
Before starting design:
- All requirements are documented and clear
- Ambiguities have been resolved with stakeholders
- Non-requirements are explicitly stated
- Acceptance criteria are defined
- Edge cases are identified
Actions:
- Review requirements document
- Identify any unclear items
- Get explicit confirmation on ambiguous points
- Document answers
Gate 2: Design Verification
Before starting implementation:
- Design addresses all requirements
- Technical approach is validated
- Interfaces are defined
- Data model is complete
- Error handling is planned
- Design has been reviewed (self or peer)
Actions:
- Walk through design against requirements
- Review with rubber duck or teammate
- Check for missing pieces
- Get approval to proceed
Gate 3: Implementation Verification
Before calling task complete:
- Code compiles/runs without errors
- All tests pass
- New code has test coverage
- Code follows project conventions
- No obvious bugs or issues
- Dependencies are appropriate
Actions:
- Run full test suite
- Self-review the diff
- Check for code smells
- Verify against acceptance criteria
Gate 4: Integration Verification
Before merging:
- Feature works end-to-end
- Integration tests pass
- No regression in existing functionality
- Performance is acceptable
- Documentation is updated
Actions:
- Test the full user flow
- Run integration test suite
- Compare performance metrics
- Review documentation changes
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 · 282 lines · 94 tokens per session scan A 8562805acb1b
verification-gates is a skill published in the GitHub repository rohitg00/skillkit (1,558 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 94 tokens to every session and 1,574 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-30.
Other skills, from other repositories
dos-verify-done-claims
Before accepting an agent's 'done / shipped / fixed' claim, verify it against ground truth (git ancestry + the commit's own diff) using the DOS kernel's dos verify and dos commit-audit — never the agent's own narration.
Verification Before Completion
Mandatory empirical verification suite execution before declaring task completion.
pytest-expert
Pytest fixtures, parametrize, mock/monkeypatch, async testing with pytest-asyncio, and coverage reporting.
user-research-cookiy
End-to-end user research assistant — qualitative and quantitative. Use this skill whenever the user mentions user research, user interviews, discussion guides, interview guides, research plans, qualitative research, quantitative research, user surveys, survey design, usability studies, participant recruitment…
best-practices
Transforms vague prompts into optimized Claude Code prompts. Adds verification, specific context, constraints, and proper phasing. Invoke with /best-practices.
curate-a-team-library
Use when building a managed team skills library for a real stack. Map work to shelves, browse before curating, write meaningful whyHere notes, and create a starter pack once the first pass is solid.