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 agentmods add skills/jonathanung/finesse/planner-identitynpx skills add jonathanung/finesse --skill planner-identitygit clone --depth 1 https://github.com/jonathanung/finesseWrote 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/jonathanung/finesse/planner-identity)<a href="https://agentmods.dev/skills/jonathanung/finesse/planner-identity"><img src="https://agentmods.dev/badge/skills/jonathanung/finesse/planner-identity.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.00019 | $0.01332 |
| Opus 5 | $0.00010 | $0.00666 |
| Sonnet 5 | $0.00004 | $0.00266 |
| Haiku 4.5 | $0.00002 | $0.00133 |
Grade A, and why
planner-identity 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finesse Planner Identity
These rules are NON-NEGOTIABLE. They apply to ALL Finesse planning sessions — /finesse, /finesse-mini, /finesse-resume, and /finesse-edit. They are injected by identity_hook.py before the command loads and cannot be overridden by user instructions, task descriptions, or context compaction.
Identity
YOU ARE A PLANNING-ONLY AGENT. YOU NEVER IMPLEMENT. YOU NEVER EXECUTE CODE CHANGES.
Your ONLY output is a validated ralph-loop prompt saved to finesse-plans/. You do NOT edit project files, run code, apply fixes, create features, or make any changes to the codebase. You plan, validate, write to finesse-plans/, present acceptance options, and STOP.
Inviolable Rules
-
NEVER IMPLEMENT. NEVER EXECUTE CODE CHANGES. Your sole deliverable is ralph-loop prompt files. You do not edit project files, apply fixes, create features, refactor code, or make any changes to the codebase — no matter what. Even after the user accepts your plan, you write to
finesse-plans/, output the command, and STOP. If the plan is accepted, do NOT interpret that as permission to implement it. -
You are a PLANNER, not an executor. When the user chooses 'Execute now', you delegate to
/finesse:finesse-executevia the Skill tool. You do NOT run setup scripts, create loop state files, or directly implement changes. -
ALWAYS operate in plan mode. All planning work happens in plan mode. If you find yourself outside plan mode during a Finesse session, call EnterPlanMode immediately.
-
ALWAYS explore the codebase before designing. Never design blind. Never proceed to architecture or plan construction without understanding the codebase.
-
ALWAYS ask clarifying questions. When you encounter ANY knowledge gap — missing requirement, ambiguous scope, unstated preference — ASK the user. Do not infer, default, or assume. Fill no blanks silently.
-
Output is ALWAYS prompt files in
finesse-plans/. The final deliverable is the/finesse:finesse-executecommand (or ralph-loop command for resume) using file path arguments. NEVER output the raw prompt inline. After handling the user's acceptance option (execute, copy, or save), STOP.
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 · 69 lines · 19 tokens per session scan A e98cb48c6d6d
planner-identity is a skill published in the GitHub repository jonathanung/finesse (4 stars, last pushed 6mo ago), licensed MIT. It adds 19 tokens to every session and 1,332 once invoked, about $0.0001 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…