Borrowing it
Nothing to install: this file belongs to justomsharma/github-resume-assistant. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/justomsharma/github-resume-assistant/main/.claude/skills/plan-first/SKILL.mdgit clone --depth 1 https://github.com/justomsharma/github-resume-assistantWrote 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/justomsharma/github-resume-assistant/plan-first)<a href="https://agentmods.dev/skills/justomsharma/github-resume-assistant/plan-first"><img src="https://agentmods.dev/badge/skills/justomsharma/github-resume-assistant/plan-first/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/justomsharma/github-resume-assistant/plan-first"><img src="https://agentmods.dev/badge/skills/justomsharma/github-resume-assistant/plan-first.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.00064 | $0.00501 |
| Opus 5.5 | $0.00026 | $0.00200 |
| Sonnet 5.5 | $0.00013 | $0.00100 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
plan-first 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 2mo 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.
What it actually says
plan-first
The rule this project lives by: never code before the approach is validated.
When the user asks for anything that would change code, do NOT start editing. Run this sequence first.
Step 1 — Understand the request
Restate what the user is asking for in one sentence. If it's ambiguous, ask a clarifying question before going further.
Step 2 — Read the existing code FIRST
- Read
docs/PRODUCT.md,docs/ROADMAP.md, anddocs/ARCHITECTURE.mdto ground yourself in what we're building and where code belongs. - Use Glob/Grep/Read to find the files this change touches. Read them.
- Identify existing patterns, utilities, and models you should reuse instead of reinventing. Note where the new code belongs per ARCHITECTURE.md.
Step 3 — Check it against the roadmap
- Which ROADMAP.md item is this? If it's not on the roadmap, flag it: is this scope creep, or should the roadmap be updated first?
- Confirm we're building versions in order (don't pull v2 work into v1).
Step 4 — Form 1–2 approaches
For the chosen work, write a short approach:
- What files change / get created (mapped to ARCHITECTURE.md layout).
- Key decisions (data shapes, where logic lives,
core/vsserver/vsclients/). - Edge cases to handle (especially the empty-GitHub case).
- What tests will prove it works (per TESTING.md).
If there's a real fork in the road, present 2 approaches with tradeoffs.
Step 5 — Validate with the user (STOP here)
Present the approach and wait for approval. Use AskUserQuestion if there's a real choice. Do not write code until the user confirms the approach.
Handoff
Once the user approves the approach → hand off to /implement.
Pass along: the approved approach, the files to touch, and the test plan.
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.
- 2mo ago First seen · 51 lines · 64 tokens per session scan A 79fde2504ef2
plan-first is a skill published in the GitHub repository justomsharma/github-resume-assistant (0 stars, last pushed 3mo ago), licensed MIT. It adds 64 tokens to every session and 501 once invoked, about $0.0003 per session on Opus 5.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
ssh-incident
A diagnosis order for "the server is down", "the site is slow", "something broke". Use when investigating a problem on a remote server through the ssh tools, before changing anything.
ssh-restricted
What to do when an ssh tool refuses to run: security modes (readonly, restricted) and human approval. Use when a command is denied, refused, or seems to hang waiting for something.
omakase-chef
Proactive Claude skill discovery and onboarding. Trigger at the start of a new session or project, when the user asks "what should I do/install/use", when no skills are installed yet, or when the user repeats a manual task 3+ times. Observe quietly, serve one precise recommendation, install on approval, and guide the…
affiliation-map
A company-affiliation map built from Russian business registry records. It links founders, managers, related companies, registration details, and bankruptcy information.
recurrent-payment
A recurring-payment workflow for T-Kassa, a payment service. It links a customer's card during an initial payment and later charges that saved payment authorisation for a subscription.
template-newsletter
An email campaign workflow that sends a saved UniSender template to a selected mailing list. It requires confirmation before sending and then reports delivery, opens, clicks, bounces, and unsubscribes.