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 Rish-Modi/career-agent --skill helpgit clone --depth 1 https://github.com/Rish-Modi/career-agentWrote 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/rish-modi/career-agent/help)<a href="https://agentmods.dev/skills/rish-modi/career-agent/help"><img src="https://agentmods.dev/badge/skills/rish-modi/career-agent/help/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/rish-modi/career-agent/help"><img src="https://agentmods.dev/badge/skills/rish-modi/career-agent/help.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.00080 | $0.01747 |
| Opus 5.5 | $0.00032 | $0.00699 |
| Sonnet 5.5 | $0.00016 | $0.00349 |
| Haiku 4.5 | $0.00008 | $0.00175 |
Grade D, and why
help scanned grade D with 2 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 1mo 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
- **If the user asks about a workflow that isn't in the recipes above**, build a recipe on the fly from the skill descriptions. Don't refuse just because there's no canned answer. Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
- **Don't include skills that aren't actually installed.** If `.claude/skills/<name>/` doesn't exist, drop it from the directory. The table above is the canonical list **only** if it matches `ls .claude/skills/` — verify The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 1mo ago First seen · 120 lines · 80 tokens per session scan D 55eb5fd19434
help is a skill published in the GitHub repository Rish-Modi/career-agent (3 stars, last pushed 4mo ago), with no licence file. It adds 80 tokens to every session and 1,747 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it D with 2 findings (tells the agent never to refuse, enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
yupi-skill
A response-style skill that makes the agent answer as 程序员鱼皮, a Chinese programming educator and entrepreneur.
propose
Draft a Kauri decision for human review before recording it. This skill should be used proactively — when the user makes, confirms, or rejects a non-trivial choice (picking a library, rejecting an approach, choosing an architecture, resolving a trade-off, establishing a convention), invoke this skill to draft a…
consult
Consult existing Kauri decisions before planning or implementing changes. Use BEFORE making architectural choices, changing conventions, picking libraries, or modifying files that might be covered by a recorded decision.
review
Review recent code changes against Kauri decisions. Use after implementing changes, before committing, during PR review, or when asked "does this look right?" to verify consistency with recorded decisions.
check-staleness
Check if recorded Kauri decisions are stale. Use when assessing code changes, reviewing decisions, or when a staleness warning was raised by a hook.
record-decision
Record a project decision using Kauri. Use when you've chosen an architectural pattern, library, convention, boundary, or resolved a trade-off.