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 agent-devWrote 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/project-init)<a href="https://agentmods.dev/skills/abilityai/abilities/project-init"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/project-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/project-init"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/project-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.00139 | $0.07766 |
| Opus 5.5 | $0.00056 | $0.03106 |
| Sonnet 5.5 | $0.00028 | $0.01553 |
| Haiku 4.5 | $0.00014 | $0.00777 |
Grade B, and why
project-init scanned grade B with 1 finding 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 6d 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
TEMPLATE="$(ls .claude/skills/project-init/PROJECT_STANDARD.template.md "${CLAUDE_PLUGIN_ROOT:-/nonexistent}/skills/project-init/PROJECT_STANDARD.template.md" 2>/dev/null | head -1)" How it starts
The opening of the file, as written. The whole thing — 356 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Init
ℹ️ 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.project-init v1.5.1 — recent: arguments no longer break the config resolver. Then proceed.
Purpose
Bring a long-term project under standardized management: create its registry and its workspace, both conforming to PROJECT_STANDARD.md. The registry is a GitHub epic issue (external, the default) or the workspace itself (internal, --internal — standard §16: project.md + tasks/ + log.md, no GitHub). After init, /project-steward manages the project autonomously in either mode.
State dependencies
| Source | Location | Read | Write |
|---|---|---|---|
| Convention doc | PROJECT_STANDARD.md (repo root) or fleet/project-standard.md (orchestrator) — §0 is the configuration |
Yes | No |
Fleet map / narrative (optional, §0 fleet.*) |
fleet/system-map.yaml (valid owner names), fleet/orchestration.md §3b (default owner) |
Yes | No |
| GitHub issues + labels | the $REGISTRY repo via gh |
Yes | Yes |
| Project workspace (agent level) | project_files/<slug>/ |
Yes | Yes |
Project workspace (--canon) |
<x-canon.clone_path>/projects/<slug>/ — the canon's shared projects zone |
Yes | Yes (the shared zone every agent writes directly; push = /canon-publish) |
| Canon declaration | template.yaml → x-canon: (repo, clone_path, folder) |
Yes (--canon only) |
No |
Platform mode (Trinity Projects — standard §17)
On a Trinity instance with Projects enabled, the platform holds the project record (ruling R38) and this skill works against it. Without Trinity, or where Projects is not enabled, nothing in this section applies and the skill runs exactly as written below.
Check once per run, after the standard is resolved. PLATFORM=$(cfg platform auto). Platform mode is off when that is off, or when this session has no mcp__trinity__list_projects tool. Otherwise call mcp__trinity__list_projects:
What ships with it
1 file beside SKILL.md 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.
- 6d ago Changed · +1 lines 957e5723d7db
- 7d ago Changed · +29 lines 030cb33bfd85
- 9d ago Changed · +28 lines · +33 tokens per session 0e08befd302b
- 11d ago Changed · +123 lines · +53 tokens per session 6721a48612c2
- 1mo ago First seen · 175 lines · 53 tokens per session scan B c1bd17d4b266
project-init is a skill published in the GitHub repository Abilityai/abilities (12 stars, last pushed 3d ago), licensed MIT. It adds 139 tokens to every session and 7,766 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it B with 1 finding (enumerates other installed skills). 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…