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/Abilityai/abilitiesWrote 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/abilityai/abilities/dev-methodology)<a href="https://agentmods.dev/plugins/abilityai/abilities/dev-methodology"><img src="https://agentmods.dev/badge/plugins/abilityai/abilities/dev-methodology/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/abilityai/abilities/dev-methodology"><img src="https://agentmods.dev/badge/plugins/abilityai/abilities/dev-methodology.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dev-methodology 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": "dev-methodology",
"description": "Documentation-driven development methodology with 24 skills, 3 agents, and project memory templates. Implements a 4-stage SDLC (Todo → In Progress → In Dev → Done) with a full pipeline: autoplan, implement, review, cso, validate-pr, and weekly invariant checks.",
"version": "1.2.1",
"author": {
"name": "Ability.ai",
"email": "[email protected]"
},
"license": "MIT"
}
What it installs
The manifest is a name and a version. 18 skills, 3 agents travel with it, and installing the plugin installs all of them — 647 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill generate-user-docs A 26 tokens
- Skill cso A 47 tokens
- Skill init A 35 tokens
- Skill implement A 27 tokens
- Skill security-check A 32 tokens
- Skill validate-architecture A 42 tokens
- Skill validate-pr A 19 tokens
- Skill feature-flow-analysis A 20 tokens
- Skill release A 41 tokens
- Skill validate-schema A 39 tokens
- Skill read-docs A 14 tokens
- Skill refactor-audit A 37 tokens
- Skill sync-feature-flows A 29 tokens
- Skill tidy A 39 tokens
- Skill update-docs A 25 tokens
- Skill add-testing A 17 tokens
- Skill security-analysis A 33 tokens
- Skill validate-config C 37 tokens
- Agent feature-flow-analyzer A 32 tokens
- Agent security-analyzer A 28 tokens
- Agent test-runner A 28 tokens
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 First seen · 11 lines scan A 0c9ed21d9414
dev-methodology is a plugin published in the GitHub repository Abilityai/abilities (12 stars, last pushed 3d 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
before-you-build
Pre-build product risk review for founders, product teams, and AI-assisted builders before implementation starts.
obw
Obsidian Workspace — project-scoped vault productivity (capture / notes / PM). Skills own folder layout and templates; /obw:pm splits a spec into blocking tickets; /issue is a Claude Mod pane that lists a view of the project's dashboard, draws Mermaid as text diagrams, and can open a card in the browser through viz.…
feature-to-pr-factory
Turn one feature into dependency-ordered GitHub or GitLab issues, then build each ticket into its own reviewed, tested PR or MR with agents.
mission-control
SDLC management for Operations, Asgard, and CAMPPS: prepared issue drafts, live schema sync, board schemas, labels, project fields, metrics, and card validation.
feishu-calendar
Manage Feishu (Lark) calendar events — create, read, update, delete events and manage attendees via the Feishu Open Platform Calendar API v4.
gse
GSE-One — AI engineering companion for structured SDLC management. 24 commands, adaptive risk analysis, unified backlog, knowledge transfer, worktree isolation.