Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Abilityai/abilities/plugin install dev-methodologyWrote 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/skills/abilityai/abilities/init)<a href="https://agentmods.dev/skills/abilityai/abilities/init"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/init/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/skills/abilityai/abilities/init"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/init.svg" alt="Reviewed on agentmods" width="80" 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.00035 | $0.01745 |
| Opus 5.5 | $0.00014 | $0.00698 |
| Sonnet 5.5 | $0.00007 | $0.00349 |
| Haiku 4.5 | $0.00003 | $0.00175 |
Grade A, and why
init 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.
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize Dev Methodology
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.init vX.Y — recent: <summary>. Then proceed.
Scaffold the documentation-driven development methodology into the current project.
Process
Step 1: Check Existing Setup
Check if the methodology is already initialized:
ls docs/memory/requirements.md 2>/dev/null && echo "EXISTS" || echo "NOT_FOUND"
ls CLAUDE.md 2>/dev/null && echo "EXISTS" || echo "NOT_FOUND"
If files already exist, ask the user if they want to overwrite or skip existing files.
Step 2: Gather Project Information
If $ARGUMENTS is provided, use it as the project name.
Otherwise, ask the user for:
- Project name (e.g., "My App")
- Project description (one-line)
- Repository URL (e.g.,
https://github.com/org/repo) - Backend URL (default:
http://localhost:8000) - Frontend URL (default:
http://localhost:3000)
Step 3: Create Directory Structure
mkdir -p docs/memory/feature-flows
mkdir -p docs/reports
mkdir -p docs/security-reports
mkdir -p testing/phases
Step 4: Scaffold CLAUDE.md
Read the CLAUDE.md template from the plugin:
${CLAUDE_PLUGIN_ROOT}/reference/templates/CLAUDE.md.template
Replace all placeholders with the user's values:
{{PROJECT_NAME}}-> project name{{PROJECT_DESCRIPTION}}-> description{{REPO_URL}}-> repository URL{{BACKEND_URL}}-> backend URL{{FRONTEND_URL}}-> frontend URL
Write to CLAUDE.md in the project root.
Step 5: Scaffold Memory Files
Copy each template from the plugin, removing the .template extension:
| Source (in plugin) | Destination |
|---|---|
reference/templates/requirements.md.template |
docs/memory/requirements.md |
reference/templates/architecture.md.template |
docs/memory/architecture.md |
reference/templates/roadmap.md.template |
docs/memory/roadmap.md |
reference/templates/changelog.md.template |
docs/memory/changelog.md |
reference/templates/feature-flows.md.template |
docs/memory/feature-flows.md |
reference/templates/feature-flows/_example-feature.md |
docs/memory/feature-flows/_example-feature.md |
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 · 184 lines · 35 tokens per session scan A 5429e0ffd5ef
init is a skill published in the GitHub repository Abilityai/abilities (12 stars, last pushed 3d ago), licensed MIT. It adds 35 tokens to every session and 1,745 once invoked, about $0.0001 per session on Opus 5.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-09-07.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…