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 commands/giuseppe-trisciuoglio/developer-kit/devkit.verify-skillgit clone --depth 1 https://github.com/giuseppe-trisciuoglio/developer-kitWrote 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/commands/giuseppe-trisciuoglio/developer-kit/devkit.verify-skill)<a href="https://agentmods.dev/commands/giuseppe-trisciuoglio/developer-kit/devkit.verify-skill"><img src="https://agentmods.dev/badge/commands/giuseppe-trisciuoglio/developer-kit/devkit.verify-skill.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.00029 | $0.01768 |
| Opus 5 | $0.00015 | $0.00884 |
| Sonnet 5 | $0.00006 | $0.00354 |
| Haiku 4.5 | $0.00003 | $0.00177 |
Grade A, and why
devkit.verify-skill 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 4d 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Skill: $1
Overview
You are a skill validation specialist for the Claude Code Developer Kit. Your task is to perform a comprehensive validation of the skill "$1" against all DevKit standards.
Usage
/devkit.verify-skill $ARGUMENTS
Arguments
| Argument | Description |
|---|---|
$ARGUMENTS |
Combined arguments passed to the command |
Execution Instructions
Agent Selection: To execute this task, use the following approach:
- Primary: Use
general-purposeagent with appropriate domain expertise - Or use specialized agent if available for the specific task type
Validation Process
Execute the following checks in sequence:
1. Skill Existence Check
- Search for the skill directory in the following locations (in this order):
.claude/skills/$1/(project-level)~/.claude/skills/$1/(user-level)./skills/**/$1/(any category subfolder under the reposkills/directory — recursive search)- Any other project-local plugin directories that the repository documents for skills (if present)
- Verify that a
SKILL.mdfile exists inside the found skill directory - Important: many development workflows (for example when authoring a Claude plugin or a shared skills repo) keep skills
under top-level
skills/categories (e.g.skills/langchain4j/<skill-name>). This is an acceptable and supported location for the purposes of validation and MUST NOT be treated as a false-positive or as a failure just because.claude/skills/or~/.claude/skills/do not contain the skill. - If the skill cannot be found in any of the locations above, report failure (Existence).
2. Requirements Conformance (@.docs/skills.md)
Check that the skill complies with all requirements from the official Skills documentation:
SKILL.md Frontmatter:
namefield: lowercase letters, numbers, hyphens only (max 64 characters)descriptionfield: present and descriptive (max 1024 characters). Description includes BOTH what the skill does AND when to use itallowed-toolsfield: uses valid tool names onlycategory: field, valid categorytags: field, relevant, and descriptive (no generic tags like "skill" or "devkit")versionfield: uses semantic versioning (e.g., 1.0.0) Important: Other frontmatter fields are not allowed.
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.
- 4d ago First seen · 214 lines · 29 tokens per session scan A f5d027966b31
devkit.verify-skill is a command published in the GitHub repository giuseppe-trisciuoglio/developer-kit (338 stars, last pushed 16d ago), licensed MIT. It adds 29 tokens to every session and 1,768 once invoked, about $0.0001 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 commands, from other repositories
upgrade
Upgrade the skillshare CLI binary and/or the built-in skillshare skill.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
verify
Perform a non-destructive post-implementation verification gate validating the implementation against spec.md, plan.md, tasks.md, and constitution.md.
release
Git geçmişinden hedef kitleye uygun sürüm notları oluştur.
spec-forge
Use when generating software specifications — full chain (Idea→Decompose→Tech Design + Feature Specs) or individual documents.
dd-init
Initialize product documentation structure in current directory.