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 Supersynergy/awesome-agentic-coding --skill plangit clone --depth 1 https://github.com/Supersynergy/awesome-agentic-codingWrote 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/supersynergy/awesome-agentic-coding/plan)<a href="https://agentmods.dev/skills/supersynergy/awesome-agentic-coding/plan"><img src="https://agentmods.dev/badge/skills/supersynergy/awesome-agentic-coding/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/supersynergy/awesome-agentic-coding/plan"><img src="https://agentmods.dev/badge/skills/supersynergy/awesome-agentic-coding/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.00019 | $0.00291 |
| Opus 5.5 | $0.00008 | $0.00116 |
| Sonnet 5.5 | $0.00004 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
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.
What it actually says
Planning Protocol
Task: $ARGUMENTS
Phase 1: Research (Parallel Haiku Agents)
Launch 2-3 parallel researcher agents to:
- Find existing code relevant to this task
- Find test patterns used in this project
- Find similar implementations in the codebase
Phase 2: Plan
Based on research, create a structured plan:
## Goal
[1 sentence: what does "done" look like?]
## Approach
[Which files to create/modify and why]
## Steps
1. [First change — most foundational]
2. [Second change — builds on first]
3. [Tests — verify behavior]
## Edge Cases
- [What could go wrong?]
- [What inputs are unexpected?]
## Not Doing
- [What's explicitly out of scope?]
Phase 3: Review
Present the plan and wait for user feedback before proceeding.
Rules
- NEVER write code during planning — plan ONLY
- Keep plans under 50 lines — if longer, the task should be split
- Include "Not Doing" to prevent scope creep
- Surface assumptions early — better to ask than guess wrong
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 · 49 lines · 19 tokens per session scan A c5a2be6597a3
plan is a skill published in the GitHub repository Supersynergy/awesome-agentic-coding (1 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 291 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-08-31.
Other skills, from other repositories
eval-hooks
Audit Claude Code and Codex hooks for validity, safety, and correctness across settings.json, hooks.json, config.toml, plugin, and skill or agent frontmatter hooks. Resolves each command, checks event names, handler types, matchers, exit-code and JSON decision strategy, and timeouts against each host's documented…
design-patterns
Detect, suggest, and evaluate GoF design patterns in TypeScript/JavaScript codebases. Use when refactoring code, applying singleton/factory/observer/strategy patterns, reviewing pattern quality, or finding stack-native alternatives for React, Angular, NestJS, and Vue.
eval-agents
Audit custom subagent definitions for Claude Code (.claude/agents/.md) and Codex (.codex/agents/.toml): loadability against the native schema, description overlap, model tier, tool scope, and headless-safe instructions. Use when onboarding to a project with agents, after adding or importing agents, or when the parent…
eval-skills
Audit a project or library of skills for metadata, trigger boundaries, workflow completion criteria, local resource closure, instruction economy, tool scope, effort, and routing evidence. Use before shipping skills, after importing a skill collection, or when a skill triggers too often or not at all.
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
source-command-audit-whitepapers
Audit version freshness, FR/EN parity, and metadata quality of all whitepapers and recap cards.