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 skills add anilcancakir/claude-code-plugins --skill plangit clone --depth 1 https://github.com/anilcancakir/claude-code-pluginsWrote 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/anilcancakir/claude-code-plugins/plan)<a href="https://agentmods.dev/skills/anilcancakir/claude-code-plugins/plan"><img src="https://agentmods.dev/badge/skills/anilcancakir/claude-code-plugins/plan/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/anilcancakir/claude-code-plugins/plan"><img src="https://agentmods.dev/badge/skills/anilcancakir/claude-code-plugins/plan.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.00060 | $0.00569 |
| Opus 5.5 | $0.00024 | $0.00228 |
| Sonnet 5.5 | $0.00012 | $0.00114 |
| Haiku 4.5 | $0.00006 | $0.00057 |
Grade A, and why
plan 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Planning Skill
Guidelines for creating effective implementation plans.
When to Use Planning
Plan When
- Feature spans multiple files/components
- Architecture decisions needed
- Multiple valid approaches exist
- Dependencies need coordination
- Risk of rework is high
Skip Planning When
- Single file change
- Bug fix with clear solution
- Following existing pattern exactly
- Simple CRUD operation
Planning Phases
1. Requirements Clarification
- What exactly needs to be built?
- What are the acceptance criteria?
- What constraints exist? (performance, security, compatibility)
- Is TDD expected?
2. Codebase Analysis
- Explore existing structure
- Find similar implementations
- Identify patterns and conventions
- Map dependencies
3. Solution Design
- Break into logical phases
- Order by dependencies
- Define atomic tasks
- Add verification steps
4. Documentation
- Save structured plan
- Include specific file paths
- Add verification commands
Plan File Location
.claude/plans/{YYYYMMDD}-{HHMMSS}-{slug}.md
Analysis Strategies
Standard Analysis
- Read CLAUDE.md for conventions
- Use Grep/Glob to find similar code
- Read key files to understand patterns
- Map where new code should live
Serena-Enhanced Analysis
get_symbols_overview()- file structurefind_symbol()- locate classes/functionsfind_referencing_symbols()- dependency mappingread_memory()- project knowledge
Task Granularity
Good task:
### Task 1.1: Create User Model
- **File**: app/Models/User.php
- **Action**: Create
- **Verification**: `php artisan tinker` → `new User()` works
Too vague:
### Task 1.1: Set up user system
- **Action**: Create everything for users
Verification Types
| Type | Example |
|---|---|
| Command | php artisan test --filter=UserTest |
| File Check | File exists at expected path |
| Syntax | No errors when loading file |
| Manual | User confirms behavior |
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.
- 1mo ago First seen · 103 lines · 60 tokens per session scan A 7dae1e395164
plan is a skill published in the GitHub repository anilcancakir/claude-code-plugins (6 stars, last pushed 8mo ago), licensed MIT. It adds 60 tokens to every session and 569 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
evolution-guide
Explains how Evolving Lite works when the user asks about the system, its features, or how to use it. Triggers on questions like "how does this work", "what is evolving lite", "what hooks are running", "explain the system".
alive:demo
Generate a believable, lived-in ALIVE world from a free-text persona description (custom path) or a deterministic sandbox preset. Routes the create/list/activate/deactivate/delete/status surface and orchestrates the 5-stage subagent generation pipeline.
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
alive:world
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.
alive-search
Search across all walnuts -- decisions, people, files, references, insights, log history.
alive-inbox
Scan 03Inbox/ for unrouted files, present routing suggestions.