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 plugins/theam/claude-dev-kit/claude-dev-kit/plugin marketplace add theam/claude-dev-kitgit clone --depth 1 https://github.com/theam/claude-dev-kitGrade 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 yesterday.
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.7",
"description": "Issue-to-PR workflow kit for any tech stack. Fetch a user story from your tracker (Jira, Linear, GitHub Issues, Azure DevOps) and any linked Figma designs, implement with plan approval, enforce >95% coverage and a security pass, generate e2e tests, open the PR, fix review findings, and move the ticket to review.",
"license": "Apache-2.0",
"homepage": "https://github.com/theam/claude-dev-kit",
"repository": "https://github.com/theam/claude-dev-kit",
"author": {
"name": "The Agile Monkeys",
"email": "[email protected]"
},
"keywords": [
"workflow",
"jira",
"linear",
"github-issues",
"azure-devops",
"figma",
"coverage",
"code-review",
"pull-request",
"tech-stack-agnostic"
],
"userConfig": {
"telemetry_enabled": {
"type": "boolean",
"title": "Share anonymous usage telemetry (fallback toggle)",
"description": "OFF by default. Consent is normally set by the `npm create @theagilemonkeys/dev-kit` wizard (stored in ~/.claude/dev-kit-telemetry/config.json); this is a fallback toggle. When on, sessions where the kit runs send ANONYMOUS token counts to a relay (no key in the client, no prompts/code/paths/emails/org-instance/IP). See TELEMETRY.md. Hard off: DEVKIT_TELEMETRY=0.",
"default": false,
"required": false
}
}
}
What ships with it
1 file 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.
- yesterday First seen · 34 lines scan A e8d1dd3c1fe9
fullstack-dev-kit is a plugin published in the GitHub repository theam/claude-dev-kit (11 stars, last pushed yesterday), 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-08-30.
Other plugins, from other repositories
jira-assistant-skills
Plugin marketplace listing 1 plugin: jira-assistant-skills.
sidekick
The Best Companion Tool for AI Agents.
allbeads
Multi-repo orchestration for AI agent workflows. Aggregate beads across repositories, manage contexts, and coordinate distributed work.
jira
Jira integration for issue tracking, project management, and workflow automation. Create, update, and search issues directly from Claude.
workingon
Claude Code skill and hooks that record your work in Jira, Linear, GitHub Issues, Trello or Vikunja.
dev-day
The complete developer day-loop for Claude Code + Jira: /start-session boots a senior-collaborator session (feedback memory, Jira backlog, standing plan-gate), /standup answers 'anything pending?', /bug-triage root-causes tickets, /groom preps them for estimation, /create-ticket files them, /jira-comment posts clean…