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.
git clone --depth 1 https://github.com/ihudak/ihudak-claude-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/commands/ihudak/ihudak-claude-plugins/wiki-tasks-extract)<a href="https://agentmods.dev/commands/ihudak/ihudak-claude-plugins/wiki-tasks-extract"><img src="https://agentmods.dev/badge/commands/ihudak/ihudak-claude-plugins/wiki-tasks-extract/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/commands/ihudak/ihudak-claude-plugins/wiki-tasks-extract"><img src="https://agentmods.dev/badge/commands/ihudak/ihudak-claude-plugins/wiki-tasks-extract.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.00039 | $0.00091 |
| Opus 5 | $0.00019 | $0.00046 |
| Sonnet 5 | $0.00008 | $0.00018 |
| Haiku 4.5 | $0.00004 | $0.00009 |
Grade A, and why
wiki-tasks-extract 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 3d 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
Read skills/wiki-tasks-extract/SKILL.md fully, then run the extraction workflow for: $ARGUMENTS
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.
- 3d ago First seen · 9 lines · 39 tokens per session scan A c35e5a581eb3
wiki-tasks-extract is a command published in the GitHub repository ihudak/ihudak-claude-plugins (2 stars, last pushed 6d ago), licensed MIT. It adds 39 tokens to every session and 91 once invoked, about $0.0002 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-09-05.
Other commands, from other repositories
plan-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.
write-stories
Break a feature into backlog items — user stories, job stories, or WWA format with acceptance criteria.
plan
Hierarchical planning entry point — all 11 plan verbs in one command. v3.7.2 consolidates /aura-frog:plan- (10 commands) into a single dispatcher that routes via the plan-orchestrator skill. The legacy plan- aliases still work as thin stubs.
plan-freeze
Manually freeze a plan node, cascading to descendants. Alias for /aura-frog:plan freeze (v3.7.2+).
contact-upsert
Create or update a contact, optionally assign to groups.
plan-next
Return and activate the next ready T4 task. Alias for /aura-frog:plan next (v3.7.2+).