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/justomsharma/github-resume-assistant/prompt-practicesnpx skills add justomsharma/github-resume-assistant --skill prompt-practicesgit 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/prompt-practices)<a href="https://agentmods.dev/skills/justomsharma/github-resume-assistant/prompt-practices"><img src="https://agentmods.dev/badge/skills/justomsharma/github-resume-assistant/prompt-practices.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.00066 | $0.01023 |
| Opus 5 | $0.00033 | $0.00511 |
| Sonnet 5 | $0.00013 | $0.00205 |
| Haiku 4.5 | $0.00007 | $0.00102 |
Grade A, and why
prompt-practices 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 5d 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.
prompt-practices
The rule: every prompt we send to Claude is code. Write it to be read, grounded, and testable — never a vibe.
When you write or change any prompt string that goes to the Anthropic API in this
project, follow this. It pairs with docs/CODING_PRACTICES.md (the API-clients and
model-id rules) and the claude-api skill (SDK usage, model ids, params).
Where prompts live (non-negotiable)
- Prompts are assembled in
clients/anthropic.py, one function per tool's prompt (ARCHITECTURE.md: clients own prompt assembly).core/never builds prompts. - The model id comes from
config.anthropic_model, never hardcoded in the prompt or the call. - Keep the prompt text in a named module-level constant or a small builder function so a test can assert what we send.
The seven rules for a good prompt here
-
Assign a role + task in one line. Start the system prompt with who Claude is and the single job. "You extract concrete, verifiable claims from an engineer's resume." One responsibility per prompt — mirror the "functions do one thing" rule.
-
Ground every instruction in the real input. Our whole moat is grounding in real data (PRODUCT.md). Tell Claude to use only the supplied resume/GitHub text and to never invent facts not present in the input.
-
Separate instructions from data. Put the user's resume text inside clear delimiters (XML tags like
<resume>...</resume>), so injected text in the resume can't be read as instructions. Never string-concatenate user text into the middle of an instruction sentence. -
Demand structured output and specify the schema. Ask for JSON matching an exact shape (field names, types), and say "return only the JSON, no prose." This is what
core/parses intoClaimdataclasses — the shape is a contract, so state it explicitly and keep it in sync withcore/models.py. -
Handle the empty / thin case in the prompt itself. Our real user has a near-empty resume or GitHub (PRODUCT.md). Tell Claude what to do when there's little to extract: return an empty list, not fabricated claims. Never let the prompt pressure Claude into inventing content to "find something."
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.
- 5d ago First seen · 81 lines · 66 tokens per session scan A eaa35317480d
prompt-practices is a skill published in the GitHub repository justomsharma/github-resume-assistant (0 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 1,023 once invoked, about $0.0003 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
model-context
MCP (Model Context Protocol) - Build AI-native servers with tools, resources, and prompts. TypeScript/Python SDKs for Claude Desktop integration.
mistral-router
Picks the right Mistral model and tool for a given task. Use when the user asks "which Mistral model should I use for X", or when you (Claude) need to route a subtask to a Mistral capability and aren't sure which model/tool fits best.
Codex-prompt
Write or improve prompts for Codex using Anthropic's official best practices. Creates system prompts, agent prompts, tool descriptions, and MCP resource templates. Pass an existing prompt to improve it, or describe what you need to create one from scratch.
octave-ultra-mythic
Ultra-high density compression using mythological atoms and semantic shorthand. Preserves soul and constraints at 60% compression for identity transmission, binding protocols, and extreme token scarcity.
build-mcp-server
MCP (Model Context Protocol) - Build AI-native servers with tools, resources, and prompts. TypeScript/Python SDKs for Claude Desktop integration.
gpt-image-2-prompt-architect
Research real GPT Image 2 prompt examples and turn rough image ideas into structured prompt packs, reference-image edit instructions, product visuals, layouts, and debugging loops. Use for prompt search, prompt rewriting, ecommerce images, readable text, posters, social creatives, character sheets, storyboards, or…