Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/epics)<a href="https://agentmods.dev/skills/unique-divine/jiyuu/epics"><img src="https://agentmods.dev/badge/skills/unique-divine/jiyuu/epics.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.00060 | $0.02563 |
| Opus 5 | $0.00030 | $0.01282 |
| Sonnet 5 | $0.00012 | $0.00513 |
| Haiku 4.5 | $0.00006 | $0.00256 |
Grade A, and why
epics 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 6d 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Epics+ Management
Navigate, interpret, and manage Epics+ docs in the boku repository. Use this skill to understand the status and priority of work, and to use the epics-plus tooling.
Quick Start and Usage Modes
- Check active work: Read epics/INDEX.md for the current dashboard of active epics grouped by priority.
- Verify/Scan: To see all epics with frontmatter or validate them:
cd /home/realu/ki/boku/epics && just epics-plus scan --fm-only --strict - Regenerate index: If you've modified frontmatter or added an epic, update the dashboard:
cd /home/realu/ki/boku/epics && just epics-plus index
Interpreting Epics+ Frontmatter (Reader View)
When reading an epic doc, look at the YAML frontmatter at line 1 for context:
- status:
active|inactive|done|archived. - priority:
p0(urgent) top3(someday).p2is default. - epic_kind:
spec|journal|reference. - tags: Broad themes (e.g.,
sai,evm,slashing). Use for "related work" queries. - repos: Which codebase this epic targets (e.g.,
nibi-chain,sai-keeper). These use the conventional repo names from the/repo-mapskill. - related_context: Links to other epics (
/epics/...). Follow these for relevant parent, child, and peer context. - agent_skills: Cursor skill IDs relevant to this epic. Suggest using them when working on the task.
Epic Structure and Creation
Epics+ metadata stays flat. Frontmatter identifies a Markdown document as an epic; its path indicates whether it is standalone, a parent, or a child:
- The unqualified term epic may refer to any of these three forms. An
epic document is any Markdown file with valid Epics+ frontmatter,
including a parent
README.mdor a child epic file. Do not assume that every request for an epic means one standalone file; infer a file or directory from the number of cohesive outcomes and related files involved. - A standalone epic is one frontmatter-bearing Markdown file directly under
epics/. - A parent epic is the frontmatter-bearing
README.mdat the root of an epic directory. It is the canonical entry point and indexes the child epics. - A child epic is a frontmatter-bearing Markdown file within an epic directory. It represents an independently trackable outcome within the parent epic.
- Other files may live beside the epic documents. Without Epics+ frontmatter, treat them as context, artifacts, or implementation material rather than additional epics.
What ships with it
2 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.
- 6d ago First seen · 255 lines · 60 tokens per session scan A b9fe43a8221f
epics is a skill published in the GitHub repository Unique-Divine/jiyuu (6 stars, last pushed 24d ago), licensed MIT. It adds 60 tokens to every session and 2,563 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-31.
Other skills, from other repositories
diet-remove
Remove a dependency identified by uzomuzo diet — analysis + issue (default) or direct PR.
clickup-cli
ClickUp CLI for managing tasks, sprints, comments, statuses, Docs, and archiving. Use when the user needs to interact with ClickUp — creating/editing/archiving tasks, checking sprint status, adding comments, linking PRs, managing Docs and pages, or searching tasks. Includes a generic clickup api passthrough covering…
diet-evaluate-removal
Data-driven deep evaluation of whether a dependency is worth removing.
miro-workflow
Compose Miro boards from natural-language requests by combining tools from miro-mcp-server. Use when the user asks to set up a sprint board, retrospective, brainstorming session, user story map, kanban, or any structured Miro layout. Do NOT use for single-tool calls (create one sticky), questions about Miro the…
bv
Beads Viewer - Graph-aware triage engine for Beads projects. Computes PageRank, betweenness, critical path, and cycles. Use --robot- flags for AI agents.
miro-boards
Create and manage Miro board content including stickies, shapes, connectors, diagrams, and mindmaps. Use for whiteboard collaboration, sprint planning, retrospectives, and brainstorming.