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 skill-coregit 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/skill-core)<a href="https://agentmods.dev/skills/ikenga-hq/ikenga-pkgs/skill-core"><img src="https://agentmods.dev/badge/skills/ikenga-hq/ikenga-pkgs/skill-core/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/skill-core"><img src="https://agentmods.dev/badge/skills/ikenga-hq/ikenga-pkgs/skill-core.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.00169 | $0.00806 |
| Opus 5 | $0.00084 | $0.00403 |
| Sonnet 5 | $0.00034 | $0.00161 |
| Haiku 4.5 | $0.00017 | $0.00081 |
Grade A, and why
skill-core 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
skill-core — the lean identity hub
This file is a router. skill-core is the hub of the skill graph: every
domain skill declares depends_on: ['skill-core'] (a one-way star, G-04,
lint-enforced in 06-skill-action-contract.md §5). skill-core itself depends on
nothing (depends_on: []).
Lean hub (founder decision, 2026-05-30). skill-core ships exactly one action —
setup, the per-project identity generator. It carries no domain logic, no shared lore / editorial bundle, and no shared query / pipeline base. Those are deferred (R-03 query-collapse, R-04 pipeline base). The single job of this package is to resolve thedepends_on: ['skill-core']edge and to localise project identity that the domain skills read.
Purpose (one line)
Generate and maintain the per-project identity instance file
(.atelier/skill-core/manifest.json) that the domain skills localise against.
Actions
| Action | File | Mode | One-liner |
|---|---|---|---|
setup |
actions/setup.md |
streaming |
Infer the project's identity (brand, founder voice, product, ICP) and write .atelier/skill-core/manifest.json. |
The setup action conforms to the locked ActionFrontmatter Zod schema in
plans/atelier/drafts/action-frontmatter.ts and is the worked example B in
06-skill-action-contract.md §8.
Routing
| If the user says… | Load | Then |
|---|---|---|
| "set up the project", "configure identity", "setup skill-core", "who are we" | actions/setup.md |
ai_infer (draft from repo) or interview mode; confirm in chat; write .atelier/skill-core/manifest.json |
What skill-core does NOT do
- No domain logic — no briefing, triage, sends, finance, content, research, or strategy actions. Those live in the domain skills.
- No shared lore / editorial bundle — deferred. skill-core is identity only.
- No shared query / pipeline base — deferred (R-03 / R-04).
- No DB reads or writes —
setupwrites only the.atelier/project-config instance file via the hostfscapability. Nosqlite, no Supabase.
What ships with it
1 file 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 · 82 lines · 169 tokens per session scan A c04afa3cc338
skill-core is a skill published in the GitHub repository ikenga-hq/ikenga-pkgs (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 169 tokens to every session and 806 once invoked, about $0.0008 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…