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 instructions/pau-vega/devkit-ai/claude-mdgit clone --depth 1 https://github.com/pau-vega/Devkit-AIWrote 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/instructions/pau-vega/devkit-ai/claude-md)<a href="https://agentmods.dev/instructions/pau-vega/devkit-ai/claude-md"><img src="https://agentmods.dev/badge/instructions/pau-vega/devkit-ai/claude-md.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.1 | $0.02341 | $0.02341 |
| Opus 5 | $0.01171 | $0.01171 |
| Sonnet 5 | $0.00468 | $0.00468 |
| Haiku 4.5 | $0.00234 | $0.00234 |
Grade A, and why
Devkit-AI CLAUDE.md 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 5d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Notes
This file is the developer-handoff for AI assistants working in this repository.
It is not specific to any single runtime — the marketplace ships plugins for
Claude Code, Cursor, and OpenCode from a single source tree, and the
installer (npx devkit-ai) translates per-target.
Project Overview
A multi-runtime plugin marketplace containing three plugins:
typescript-rules, jsdoc-standards, and commit-commands. The marketplace
ships an npx devkit-ai installer that copies the plugins into Claude Code,
Cursor, or OpenCode at any of three scopes (project, project-local, user).
The marketplace is being extended so all three runtimes get the same
skill / command / hook surface.
The repo is mostly markdown, JSON configs, shell scripts, and a static HTML
landing page — but there is also a Node-based installer
(bin/install.mjs + src/installer/*.mjs, ESM, one runtime dep:
@clack/prompts). The build step for the landing page is a single bash script.
Repository Structure
.claude-plugin/marketplace.json— Marketplace manifest declaring all three plugins. The.claude-plugin/directory is Claude Code's conventional manifest path; the installer's source-of-truth is the JSON inside it, not the directory name.plugins/typescript-rules/— TypeScript conventions plugin (agent, command, skill, hooks)plugins/jsdoc-standards/— JSDoc documentation plugin (agent, command, skill, hooks)plugins/commit-commands/— Git workflow plugin (commands, agents, skill; no hooks).cursor/skills/— Cursor-readable symlinks to each plugin's skills (generated by the build script)package.json+bin/install.mjs+src/installer/*.mjs—devkit-ainpm package, an@clack/prompts-based installer that copies the plugins into Claude Code, Cursor, or OpenCode at any of three scopesmarketplace.html— Static landing page rendered to GitHub Pages, embeds plugin metadata viaconst PLUGINS = [...]scripts/build-marketplace.sh— Discovers components in each plugin, generates.cursor/skills/symlinks, and injects fresh JSON intomarketplace.html.github/workflows/deploy-pages.yml— Runs the build script and deploysmarketplace.htmlto Pages on every push.github/workflows/release-please.yml— Release-please +npm publishto the public npm registry
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.
- 5d ago First seen · 199 lines · 2,341 tokens per session scan A 8d6051c839bf
Devkit-AI CLAUDE.md is an instructions file published in the GitHub repository pau-vega/Devkit-AI (2 stars, last pushed 20d ago), licensed MIT. It adds 2,341 tokens to every session, about $0.0117 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 instructions, from other repositories
cc-thingz CLAUDE.md
Instructions for umputun/cc-thingz, covering claude.md, repository purpose, key rules, conventions and structure.
swe-marketplace CLAUDE.md
Instructions for andisab/swe-marketplace, covering claude.md, what this repo is, repo layout, field rules (enforced by the generator) and common workflows.
opencode-plugin AGENTS.md
AGENTS.md instructions for gzb1128/opencode-plugin, covering agents.md — opencode-plugin, 项目概述, 设计原则, 导航 and 关键隐式知识.
agent-skills CLAUDE.md
Instructions for mindbox-cloud/agent-skills, covering agent-skills — developer guide for claude code, repository purpose, repository structure, how to add a new plugin and step 1 — create the directory structure.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).