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 Unique-Divine/jiyuu --skill md-tasksgit clone --depth 1 https://github.com/Unique-Divine/jiyuuWrote 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/unique-divine/jiyuu/md-tasks)<a href="https://agentmods.dev/skills/unique-divine/jiyuu/md-tasks"><img src="https://agentmods.dev/badge/skills/unique-divine/jiyuu/md-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.00082 | $0.00860 |
| Opus 5 | $0.00041 | $0.00430 |
| Sonnet 5 | $0.00016 | $0.00172 |
| Haiku 4.5 | $0.00008 | $0.00086 |
Grade A, and why
md-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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Markdown tasks and checkbox conventions
Follow these conventions so agents and humans can scan open work reliably.
Usage guidelines
Checkbox notation
Denote open tasks or TODOs with standard checkbox notation:
- [ ]for incomplete tasks.- [x]for done tasks.
Indentation defines subtasks: extra leading spaces nest bullets under a parent item.
In planning/spec documents, default every actionable item at every nesting level to checkbox notation. Do not hide implementation work in ordinary bullets.
Often add ordinary sub-bullets for status or context beneath a task, but only when the bullet is not itself work to do. For example:
- [ ] Some task
- Status: maybe some status description or how it was completed
- More context
- [ ] Subtask A
This keeps review tight: unfinished work sorts visually to checklist lines while still allowing narrative detail.
Actionable sub-bullets
If a sub-bullet describes work to do, a decision to resolve, behavior to implement, a file to create, a test to add, or an acceptance criterion to verify, write it as a checkbox task too:
- [ ] Implement tx archive CLI.
- [ ] Keep Bash responsible for chain config, keyring preflight, and broadcast.
- [ ] Make TypeScript responsible for txhash parsing and Markdown formatting.
- Rationale: TypeScript is easier to test for JSON, filenames, and CLI args.
Use ordinary nested bullets only for non-actionable context, rationale, status,
examples, or notes. When unsure whether a sub-bullet is actionable, prefer
- [ ].
Task Questions
Sometimes we'll pose a question or frame a resolve decision as a task. That can look like this.
- [ ] Q: Some open question?
A: Record the answer once resolved, mark this decision task complete, and
create separate open tasks for its actionable consequences.
Decision and implementation tasks
Deciding what to do and implementing that decision are different task lifecycles. During specification, track an unresolved decision as an open task. Once resolved, preserve the decision and rationale as settled context or a completed decision task, then derive separate open tasks for implementation, validation, rollout, or deferred follow-up:
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 · 112 lines · 82 tokens per session scan A 34ba3a37bc4a
md-tasks is a skill published in the GitHub repository Unique-Divine/jiyuu (6 stars, last pushed 25d ago), licensed MIT. It adds 82 tokens to every session and 860 once invoked, about $0.0004 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-31.
Other skills, from other repositories
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
mma-investigator
Expert system for investigating MMA (Multi-Metric Allocator) behavior on CockroachDB clusters. Helps oncall engineers diagnose load imbalances, understand rebalancing decisions, and identify why MMA did or didn't act.
migrate-state-management
Migrate Redux or React Context to the correct state option (React Query for server state, nuqs for URL/shareable state, Zustand for global client state). Use when refactoring away from Redux/Context, moving state to the right store, or when the user asks to migrate state management.
ast-introspection
Use Go AST-aware analysis to enumerate symbols, extract signatures, and propose mechanically safe refactors (read-only by default).
code-formatter
Apply repository-standard formatting to minimize diff noise and meet linter expectations.
lsp-local-symbols
Fast file-scoped symbol analysis — find all usages of a symbol within the current file, list all symbols defined in the file, and get type info at a position. Use when you need local-scope analysis without a workspace-wide search.