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.
git clone --depth 1 https://github.com/theam/claude-dev-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/plugins/theam/claude-dev-kit/fullstack-dev-kit)<a href="https://agentmods.dev/plugins/theam/claude-dev-kit/fullstack-dev-kit"><img src="https://agentmods.dev/badge/plugins/theam/claude-dev-kit/fullstack-dev-kit/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/plugins/theam/claude-dev-kit/fullstack-dev-kit"><img src="https://agentmods.dev/badge/plugins/theam/claude-dev-kit/fullstack-dev-kit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
fullstack-dev-kit 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.
What it actually says
{
"name": "fullstack-dev-kit",
"version": "0.19.18",
"description": "Issue-to-PR workflow for any tech stack: fetch stories from Jira/Linear/GitHub/Azure and Figma designs, plan-approval gate, adaptive quality + coverage gates, e2e generation, PR creation and review.",
"author": {
"name": "The Agile Monkeys"
},
"homepage": "https://github.com/theam/claude-dev-kit",
"repository": "https://github.com/theam/claude-dev-kit",
"license": "Apache-2.0",
"keywords": [
"issue-to-pr",
"code-review",
"coverage",
"jira",
"linear",
"workflow"
],
"logo": "./assets/logo.png",
"skills": "./skills/"
}
What it installs
The manifest is a name and a version. 13 skills travel with it, and installing the plugin installs all of them — 919 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill dev-kit-setup A 81 tokens
- Skill plan-backlog A 97 tokens
- Skill create-pr A 48 tokens
- Skill fix-pr A 66 tokens
- Skill issue-fetch A 68 tokens
- Skill issue-update A 68 tokens
- Skill pr-review A 57 tokens
- Skill coverage-check A 59 tokens
- Skill figma-fetch A 40 tokens
- Skill plan-definition A 96 tokens
- Skill delegate-backlog A 107 tokens
- Skill e2e-generate A 52 tokens
- Skill follow-ups A 80 tokens
What ships with it
2 files beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed bdd425dfaaa7
- 1mo ago Changed af0484ac7623
- 1mo ago Changed 649401cb843f
- 1mo ago Changed 9012338d389a
- 1mo ago Changed · +17 lines 30181c2cb423
- 1mo ago First seen · 5 lines scan A 09ca1b075040
fullstack-dev-kit is a plugin published in the GitHub repository theam/claude-dev-kit (16 stars, last pushed 1mo ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-04.
Other plugins, from other repositories
e2e-skills
Four agent skills for Playwright and Cypress end-to-end tests: generate new Playwright specs through the installed official Playwright agents with a short rules checklist and a scanner gate, review existing specs or PR diffs, and debug failed runs.
workbench
Ticket-to-PR development workflow: triage, plan with verified citations, implement inside the plan, review, commit, PR. Pluggable issue trackers (Jira, Azure DevOps, GitHub Issues) or a backlog in the repo, so it works with no tracker at all.
slopstop marketplace
Marketplace hosting the slopstop plugin: ticket-anchored AI development for Linear, JIRA, and GitHub Issues — TDD-first planning, scope control, adversarial review, and multi-agent orchestration.
slopstop
Autonomous, ticket-anchored AI development for GitHub Issues, Linear, and JIRA, built on one idea: stop slop before it goes in, instead of reviewing it out afterwards. Work starts from a ticket, not a prompt. One command drives the whole lifecycle for one ticket or twenty at once, interleaved and unattended…
quality-assurance-suite
Find gaps that could break a release, mislead a maintainer, or make a passing test meaningless.
crap-analyzer
Analyze recently-changed code for Change Risk Anti-Patterns. Computes CRAP per changed function across TypeScript, JavaScript, Python, Java, Kotlin, Go, Ruby, C#, Rust, and PHP. Auto-discovers how the repo generates coverage and proposes refactors + test stubs.