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 strategygit 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/strategy)<a href="https://agentmods.dev/skills/ikenga-hq/ikenga-pkgs/strategy"><img src="https://agentmods.dev/badge/skills/ikenga-hq/ikenga-pkgs/strategy/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/strategy"><img src="https://agentmods.dev/badge/skills/ikenga-hq/ikenga-pkgs/strategy.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.00175 | $0.01317 |
| Opus 5 | $0.00088 | $0.00659 |
| Sonnet 5 | $0.00035 | $0.00263 |
| Haiku 4.5 | $0.00017 | $0.00132 |
Grade A, and why
strategy 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
strategy — dispatch-only OKR 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.
Pipeline-stages convention: This skill extends the R-04 Pipeline-stages convention to the strategy domain.
strategy-reviewproposals carryux_modeper the §Pipeline-stages mapping —silentfor agent-auto moves (nightly metric syncs),confirmfor operator one-offs (confirm weekly review agenda),approvefor terminal-crossing or outward-committing actions (countersign a SAFE, approve a GA checklist). The strategy ux-mode map is: O-01..O-08 carry one ofconfirm/approve/silentper the strategy screen fixture. See06-skill-action-contract.md§Pipeline-stages.
R-03 (Query-collapse): No query actions are present. Domain skills are permanently dispatch-only. Interactive questions route through
skill-query.
Purpose (one line)
Surface next-action proposals for open objectives and flag at-risk OKRs —
reading ikenga.db state (existing base tables only), never owning CRUD.
Dispatch actions
| Action | File | Mode | One-liner |
|---|---|---|---|
setup |
actions/setup.md |
streaming |
Configure the strategy skill: active cycle/quarter, objective areas, owner agents. Writes .atelier/skill-strategy/manifest.json. |
strategy-review |
actions/strategy-review.md |
approve |
Run the weekly/cycle OKR review — read open objectives and KR state, draft countersign proposals with evidence, flag at-risk objectives; pause for operator approval. |
draft-objective |
actions/draft-objective.md |
confirm |
Draft a new objective in dock chat (D-02 setup-in-chat pattern); pane/host path writes the row. |
What ships with it
4 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 · 101 lines · 175 tokens per session scan A c54983181a0c
strategy is a skill published in the GitHub repository ikenga-hq/ikenga-pkgs (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 175 tokens to every session and 1,317 once invoked, about $0.0009 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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.