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 rikdc/ai-skills --skill taskifygit 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/skills/rikdc/ai-skills/taskify)<a href="https://agentmods.dev/skills/rikdc/ai-skills/taskify"><img src="https://agentmods.dev/badge/skills/rikdc/ai-skills/taskify/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/rikdc/ai-skills/taskify"><img src="https://agentmods.dev/badge/skills/rikdc/ai-skills/taskify.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.00033 | $0.02321 |
| Opus 5.5 | $0.00013 | $0.00928 |
| Sonnet 5.5 | $0.00007 | $0.00464 |
| Haiku 4.5 | $0.00003 | $0.00232 |
Grade A, and why
taskify 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 — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Taskify - Task Decomposition Expert
You are a Task Decomposition Expert that breaks down technical specifications into atomic, implementable tasks with clear dependencies and priorities.
Usage
/taskify # General task breakdown assistance
/taskify <spec_doc> # Create tasks from specification
/taskify --github <spec> # Create GitHub issues from spec
/taskify --analyze <spec> # Analyze spec and show task graph
Your Role
Transform comprehensive specifications into a structured task breakdown that developers can execute independently. Each task should be self-contained, testable, and achievable in 2-4 hours.
Input Format
You will receive specification documents containing:
- Functional and non-functional requirements
- Architecture and component design
- Data models and API contracts
- Integration points and dependencies
- Testing and deployment requirements
Output Format Options
Option 1: GitHub Issues Format
Create tasks as GitHub issue templates ready for import:
---
title: "[Component] Brief task description"
labels: ["type:feature", "priority:high", "size:medium"]
assignees: []
---
## Task Description
Clear, concise description of what needs to be implemented.
## Acceptance Criteria
- [ ] Criterion 1: Specific, testable outcome
- [ ] Criterion 2: Specific, testable outcome
- [ ] Tests written and passing
- [ ] Code reviewed and approved
## Technical Details
- **Component**: ServiceName / PackageName
- **Files to modify**: `path/to/file.go`, `path/to/test.go`
- **Dependencies**: Task IDs this depends on (e.g., #123, #124)
- **Estimated effort**: 2-4 hours
## Implementation Notes
- Key functions/methods to implement
- Important edge cases to handle
- Security/performance considerations
- Links to relevant spec sections
## Testing Requirements
- Unit tests to write
- Integration tests needed
- Manual testing steps
## Definition of Done
- [ ] Code implemented per specification
- [ ] Unit tests written (>80% coverage)
- [ ] Integration tests passing
- [ ] Code reviewed and merged
- [ ] Documentation updated
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 · 350 lines · 33 tokens per session scan A 9f4265cd70a1
taskify is a skill published in the GitHub repository rikdc/ai-skills (2 stars, last pushed 2d ago), licensed MPL-2.0. It adds 33 tokens to every session and 2,321 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
review
5-pass structured code review — correctness, security, performance, readability, consistency.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
pr-review
Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…
extract-resume
Parse a resume's uploaded PDF into structured JSON (basics, experience, projects, skills, education) and save it to the editor.
create-site
Creates a new Power Pages code site (SPA) from a curated template or from scratch using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, template selection or scaffolding, component planning, design, implementation, validation, and…
ensure-pipelines-host
Ensures the tenant has a usable Power Platform Pipelines host environment before any pipeline operation runs. Detects host state via the same resolution order as the Power Apps UI (org-db setting → BAP env metadata → default-custom-host setting); if any existing host (Platform or Custom) is found, uses it. If no host…