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 ikenga-hq/ikenga-pkgs --skill tasksgit clone --depth 1 https://github.com/ikenga-hq/ikenga-pkgsWrote 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/ikenga-hq/ikenga-pkgs/tasks)<a href="https://agentmods.dev/skills/ikenga-hq/ikenga-pkgs/tasks"><img src="https://agentmods.dev/badge/skills/ikenga-hq/ikenga-pkgs/tasks/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/ikenga-hq/ikenga-pkgs/tasks"><img src="https://agentmods.dev/badge/skills/ikenga-hq/ikenga-pkgs/tasks.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.00119 | $0.00839 |
| Opus 5 | $0.00060 | $0.00419 |
| Sonnet 5 | $0.00024 | $0.00168 |
| Haiku 4.5 | $0.00012 | $0.00084 |
Grade A, and why
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 8d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tasks — dispatch-only tasks surface
This file is a router. Each action lives in its own file under actions/;
load on demand. The state contract (which ikenga.db tables are touched,
read-vs-write boundary, dispatch-only scope) is in lib/state.md — read it
before building any action.
skill-core note:
depends_on: ['skill-core']is declared above.skill-coreships ascom.ikenga.skill-coreonikenga-pkgsmain. Per the G-04 contract and the lint spec in06-skill-action-contract.md§5, no other target is legal.
Purpose (one line)
Produce the project roster for the tasks owner-picker and run completion sweeps
— reading ikenga.db state, never owning CRUD.
Dispatch actions
| Action | File | Mode | One-liner |
|---|---|---|---|
setup |
actions/setup.md |
streaming |
Configure the project roster (humans + agents). Writes .atelier/skill-tasks/roster.json + manifest.json. |
sweep |
actions/sweep.md |
approve |
Read completion-signal candidates from ikenga.db; produce draft close-decisions for operator approval. |
Both actions conform to the locked ActionFrontmatter Zod schema in
plans/atelier/drafts/action-frontmatter.ts. Action bodies land in WP-16.
Routing
| If the user says… | Load | Then |
|---|---|---|
| "setup task roster", "configure skill-tasks", "who should tasks be assigned to" | actions/setup.md |
ai_infer or interview mode; writes .atelier/skill-tasks/roster.json + manifest.json |
| "sweep tasks", "close done tasks", "completion sweep", "what can be closed" | actions/sweep.md |
Read tasks + evidence tables; produce close-decision list; pause for operator approval |
What skill-tasks does NOT do
- No task CRUD — create/edit/delete/reassign tasks belongs to the tasks app pkg (
com.ikenga.tasks). - No email CRUD — mail records are read-only evidence for sweep decisions.
- No cross-queue triage — cross-domain triage (email + task queue together) stays in skill-pa; this skill owns the tasks-only sweep.
- No Supabase — state is local
ikenga.dbviahost.dbQuery/host.dbExeconly. - No direct DB writes from skill — approved close-decisions dispatch through the host write path; the skill itself does not call
host.dbExec.
What ships with it
3 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.
- 8d ago First seen · 81 lines · 119 tokens per session scan A bba1a6987810
tasks is a skill published in the GitHub repository ikenga-hq/ikenga-pkgs (0 stars, last pushed today), licensed Apache-2.0. It adds 119 tokens to every session and 839 once invoked, about $0.0006 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.