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 agentmods add skills/robertguss/claude-code-toolkit/simple-tasksnpx skills add robertguss/claude-code-toolkit --skill simple-tasksgit clone --depth 1 https://github.com/robertguss/claude-code-toolkitWhat 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 | $0.00061 | $0.00321 |
| Opus 5 | $0.00030 | $0.00161 |
| Sonnet 5 | $0.00012 | $0.00064 |
| Haiku 4.5 | $0.00006 | $0.00032 |
Grade A, and why
simple-tasks 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 2d 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
Simple Tasks
Overview
Paul Solt [email protected] Version: 0.9.8
simple-tasks installs a lightweight local task CLI into an existing project.
Design goals:
- Fast local planning and execution.
- Human shorthand task numbers + stable task IDs.
- Single canonical backlog file:
tasks/TASKS.md. - Optional long-form notes per task:
tasks/details/<id>.md.
Install
skills/simple-tasks/scripts/install.sh --project-dir /path/to/project
Common flags:
--project-dir PATHrequired--mode install|upgradedefaultinstall--dry-runpreview changes only
Commands
Installed scripts/task.sh supports:
claimdonestatusnextplanfinishedupcomingneeds-planningblockedsummarylearn
Filters:
--today--last-24h--last-week--last-month--days--mine--agent--limit
What ships with it
3 files 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.
- 2d ago First seen · 57 lines · 61 tokens per session scan A 4ca649f90ab9
simple-tasks is a skill published in the GitHub repository robertguss/claude-code-toolkit (108 stars, last pushed 25d ago), licensed MIT. It adds 61 tokens to every session and 321 once invoked, about $0.0003 per session on Opus 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-30.
Other skills, from other repositories
plan-feature-from-issue
Internal step of plan-feature: turn a feature-request issue into a scoped, sized, roadmap-mapped SPEC product half (capability closure satisfied) with Closes #N traceability.
triage-issue
Verify an issue, persisted audit finding, or unresolved review finding against current code, classify it, and write only the contracted forge/ledger outcome. Supports independent batches and an immediate-fix review-finding route. Triggers: "triage-issue", "triage issue N", "triage this finding", "is this trigger met".
workflow-status
Read-only workflow sensor: compute repository, roadmap, dependency, PR, finding, and recovery state, then emit the fixed machine envelope. Never edits. Triggers: "workflow-status", "workflow status", "what can I build next", "state of the run".
execute-phase
Implement all remaining phases of a planned feature/fix by default, or one explicit P , with frozen acceptance, phase-local gates, commits, recovery, and final PR close-out. Use --fix for fix SPECs; --force is user-only.
offensive-vuln-classes
Exploit development curriculum covering core vulnerability classes with real-world CVE case studies: stack/heap buffer overflows, use-after-free, integer overflows, format strings, type confusion, and race conditions. Use when learning or teaching vuln classes, researching specific CVE patterns, or building exploit…
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.