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 softspark/ai-toolkit --skill plangit clone --depth 1 https://github.com/softspark/ai-toolkitWrote 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/softspark/ai-toolkit/plan)<a href="https://agentmods.dev/skills/softspark/ai-toolkit/plan"><img src="https://agentmods.dev/badge/skills/softspark/ai-toolkit/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/softspark/ai-toolkit/plan"><img src="https://agentmods.dev/badge/skills/softspark/ai-toolkit/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.01238 |
| Opus 5.5 | $0.00014 | $0.00495 |
| Sonnet 5.5 | $0.00007 | $0.00248 |
| Haiku 4.5 | $0.00003 | $0.00124 |
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.
Project Planning
$ARGUMENTS
Workflow
- Analyze scope: read the goal, scan relevant source files to understand current state
- Detect project type: match keywords to determine stack and primary agents (see table below)
- Break into phases: group tasks by dependency order (foundation, core, polish)
- Assign agents: map each task to the best-fit agent with explicit dependencies
- Write plan file: create
{project-slug}.mdin project root using templates/plan-template.md - Validate: confirm every requirement maps to at least one task, no circular dependencies exist, and success criteria are measurable
Project Type Detection
| Keywords | Type | Primary Agents |
|---|---|---|
| landing, website | Static Site | frontend-specialist |
| dashboard, admin | Web App | frontend + backend |
| api, rest, graphql | API Only | backend-specialist |
| mobile, ios, android | Mobile | mobile-developer |
| cli, terminal | CLI Tool | backend-specialist |
Planning Constraints
- Create plan documents only, NO code writing, NO file creation (except the plan)
- Each task must name affected file(s) and a single owning agent
- Phases must have explicit dependency edges (
Phase 1 -> Phase 2) - Success criteria must be verifiable (command to run, expected output, or observable behavior)
KB Integration
Before planning:
smart_query("project template: {type}")
hybrid_search_kb("architecture {pattern}")
Estimation & Templates
T-shirt sizing (use for >1 day work)
| Size | Effort | Example |
|---|---|---|
| XS | <2h | typo, add field |
| S | 2-4h | simple component, basic API |
| M | 1-2 days | feature with tests |
| L | 3-5 days | complex feature |
| XL | 1-2 weeks | major subsystem |
Avoid hour-precise estimates beyond a week — they are false confidence (cone of uncertainty: 4× variance at idea, 1.5× at design).
SMART tasks vs phase outcomes
Plan-level tasks should be phase-aligned outcomes ("authentication ships behind a feature flag"), not SMART implementation steps ("add JWT middleware"). The latter belongs in the issue tracker after /prd-to-issues.
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 · 35 tokens per session scan A de617d13faa7
plan is a skill published in the GitHub repository softspark/ai-toolkit (181 stars, last pushed 11d ago), licensed Apache-2.0. It adds 35 tokens to every session and 1,238 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-03.
Other skills, from other repositories
orchestrator
Providerneutrales Protokoll zum Zerlegen komplexer Aufgaben, zum Beauftragen unabhängiger Worker und zur evidenzbasierten Abnahme ihrer Ergebnisse.
workflow-extract
Baut aus einem Chatverlauf oder aus bestehenden Automatisierungs-Prompts (z. B. eines anderen Agenten-Systems) eine selbstlaufende, user-neutrale Workflow-Automatisierung: einen wiederkehrenden Prompt bzw. Automations-Skill für Cron/Schedule/Loop. Alias: automations-extractor. Nutze diesen Skill bei „mach daraus eine…
project-onboarding
Standard procedure for onboarding new software projects: Feature analysis, code quality review, onboarding checklist, and task creation.
skill-register-care
Pflege-Skill, der das dreiteilige Skill-Register konsistent hält (code-skill-index-Kataloge, Skill-Index, SKILL-MAP Family-/Routing-Map). Nutze diesen Skill für einen Drift-Check zwischen dem realen Skill-Inventar und dem dokumentierten Register: fehlende oder zu viele Einträge melden, Counts korrigieren, Stand-Datum…
file-collect-sort-action
Erkennt Nutzeraufträge der Form "hole aus einem Ordner immer bestimmte Dateien und sammle sie an einem Ziel" und richtet dafür das Modul file-collect-sort-action (CLI fcsa) ein — ein konfigurationsgetriebener Agent, der Ordner scannt, Dateien per Schablone kategorisiert und gestufte Aktionen anwendet…
data-governance-guide
Gouvernance des données incluant catalogues, lineage, qualité, ownership, politiques et metadata management. Se déclenche avec "data governance", "gouvernance données", "data catalog", "data lineage", "metadata", "data ownership".