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.
/plugin marketplace add Abilityai/abilitiesnpx agentmods add plugins/abilityai/abilities/agent-devgit clone --depth 1 https://github.com/Abilityai/abilitiesGrade A, and why
agent-dev 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "agent-dev",
"description": "Develop and extend existing agents \u2014 add skills, memory systems, GitHub Issues development workflow (backlog, roadmap, groom, claim, autoplan, commit, sprint, work-loop), long-running multi-stage pipelines (add-pipeline + heartbeat / status / recover / pause / resume runtime skills), system-aware orchestration (add-orchestrator \u2014 discover / compose / orchestrate a multi-agent system via Trinity's SystemManifest), a shared canonical-data layer (add-canon \u2014 a fleet canon repo with publish / consume / reconcile / doctor runtime skills and per-counterpart relations memory; add-canon-lint \u2014 deterministic consistency linting of the canon repo: two-zone schema, one-home-per-key facts, CI on every push), and fleet analysis + migration (agent-fleet-analysis \u2014 scan directories of agents in any paradigm, score fleet maturity / migration readiness, recommend a fleet architecture, map every gap to an installable marketplace skill, and emit a PDF report plus an agent-executable markdown work order; agent-fleet-migrate \u2014 execute that work order non-destructively: copy sources into a fresh workspace, extract logic per paradigm (n8n nodes / framework code / freeform prompts), delegate every fix to a named marketplace skill, verify each copy through the review gate, and report the before/after maturity delta with a gated Trinity deploy offer)",
"version": "1.15.1",
"author": {
"name": "Ability.ai",
"email": "[email protected]"
},
"homepage": "https://github.com/abilityai/abilities",
"repository": "https://github.com/abilityai/abilities",
"license": "MIT",
"keywords": [
"agent",
"development",
"skills",
"playbook",
"memory",
"backlog",
"github",
"issues",
"workflow",
"planning",
"file-index",
"zettelkasten",
"json-state",
"workspace",
"git-sync",
"hooks",
"durability",
"cross-session",
"pipeline",
"dag",
"stWhat 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 · 65 lines scan A 75bc716ccdb0
agent-dev is a plugin published in the GitHub repository Abilityai/abilities (11 stars, last pushed 14d ago), licensed MIT. 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.
beans-prime
Configure Claude Code to track work using Beans.
rook-claude
Claude Code plugins for rook (github.com/rook/) maintainers: maintainer-grade code review, backlog triage, systemic-PR campaigns, and rook house conventions.
rook-maintainer
Maintainer-grade skills for rook (github.com/rook/): code review, backlog triage, systemic-PR campaigns, and the rook house conventions they enforce.
ai-skills
Plugin marketplace listing 8 plugins: security-hooks, pr-review-triage, dev-skills, nix-skills, git-workflow.
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.