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/rikdc/ai-skillsWrote 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/rikdc/ai-skills/generate-tasks)<a href="https://agentmods.dev/commands/rikdc/ai-skills/generate-tasks"><img src="https://agentmods.dev/badge/commands/rikdc/ai-skills/generate-tasks.svg" alt="Measured on agentmods" 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.00000 | $0.00880 |
| Opus 5 | $0.00000 | $0.00440 |
| Sonnet 5 | $0.00000 | $0.00176 |
| Haiku 4.5 | $0.00000 | $0.00088 |
Grade A, and why
generate-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 7d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rule: Generating a Task List from a PRD
Goal
To guide an AI assistant in creating a detailed, step-by-step task list in Markdown format based on an existing Product Requirements Document (PRD). The task list should guide a developer through implementation.
Output
- Format: Markdown (
.md) - Location:
/tasks/ - Filename:
tasks-[prd-file-name].md(e.g.,tasks-prd-user-profile-editing.md)
Process
- Receive PRD Reference: The user points the AI to a specific PRD file
- Analyze PRD: The AI reads and analyzes the functional requirements, user stories, and other sections of the specified PRD.
- Phase 1: Generate Parent Tasks: Based on the PRD analysis, create the file and generate the main, high-level tasks required to implement the feature. Use your judgement on how many high-level tasks to use. It's likely to be about 5. Present these tasks to the user in the specified format (without sub-tasks yet). Inform the user: "I have generated the high-level tasks based on the PRD. Ready to generate the sub-tasks? Respond with 'Go' to proceed."
- Wait for Confirmation: Pause and wait for the user to respond with "Go".
- Phase 2: Generate Sub-Tasks: Once the user confirms, break down each parent task into smaller, actionable sub-tasks necessary to complete the parent task. Ensure sub-tasks logically follow from the parent task and cover the implementation details implied by the PRD.
- Identify Relevant Files: Based on the tasks and PRD, identify potential files that will need to be created or modified. List these under the
Relevant Filessection, including corresponding test files if applicable. - Generate Final Output: Combine the parent tasks, sub-tasks, relevant files, and notes into the final Markdown structure.
- Save Task List: Save the generated document in the
/tasks/directory with the filenametasks-[prd-file-name].md, where[prd-file-name]matches the base name of the input PRD file (e.g., if the input wasprd-user-profile-editing.md, the output istasks-prd-user-profile-editing.md).
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.
- 7d ago First seen · 62 lines · 0 tokens per session scan A 8d3aaa0f7512
generate-tasks is a command published in the GitHub repository rikdc/ai-skills (2 stars, last pushed 2d ago), licensed MPL-2.0. It costs nothing until one of its globs matches a file; then it loads 880 tokens. 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 commands, from other repositories
learn
Force claude-smart to extract learnings from this session now.
init
Install the formatters this repository needs, with every command visible before it runs.
brand-generate
Generate an on-brand document from a saved Brand Profile.
genshijin-compress
A command for safely shortening Markdown or text files into the genshijin style.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
audit-plugin
Audit plugin skills, commands, and agents for structure, size, and naming issues.