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 younnieCutler/japan-career-agent --skill challengegit clone --depth 1 https://github.com/younnieCutler/japan-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/younniecutler/japan-career-agent/challenge)<a href="https://agentmods.dev/skills/younniecutler/japan-career-agent/challenge"><img src="https://agentmods.dev/badge/skills/younniecutler/japan-career-agent/challenge/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/younniecutler/japan-career-agent/challenge"><img src="https://agentmods.dev/badge/skills/younniecutler/japan-career-agent/challenge.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.00033 | $0.00438 |
| Opus 5 | $0.00016 | $0.00219 |
| Sonnet 5 | $0.00007 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
challenge 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 12d 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
challenge — adversarial decision review
This is deliberately user-invoked. A permanently automatic objection reflex would distort the user's decision process and make every ordinary preparation task defensive.
Goal
Attack one user-approved strategy or decision plan and reduce the result to one root objection plus one cheap falsification test. The user still owns the decision.
Workflow
- Identify the exact decision and the assumptions it needs.
- Check the strongest failure axes: false facts, unsupported inference, missing evidence, hidden trade-off, unsafe scope, or a result assumed before it exists.
- Collapse related findings into one load-bearing root.
- Name the cheapest test that could show the root matters or does not matter.
- Return the objection and test for user review before the plan continues.
Rules
- Run only after explicit user opt-in or an explicitly user-confirmed consequential-decision policy.
- Do not produce a total, hiring prediction, recommendation, or decision on the user's behalf.
- Do not average independent axes or hide a confirmed hard conflict.
- One root and one test; no checklist expansion.
- This Skill is read-only and never invokes another Skill.
Gate D terminal semantics
- No meaningful load-bearing objection survives → report
completed. - A load-bearing objection is found → report
needs_approvalwith the{root, first_nail}summary; the plan must pause for the user's review before any dependent Quality Skill runs. - Do not report an objection as
completedmerely because the analysis itself finished.
Verification
Report {root, first_nail} with the evidence behind the objection. If no load-bearing objection
survives, say so and name the assumptions that remain Unknown.
Adaptation notice: ../../_shared/THIRD_PARTY_NOTICES.md.
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.
- 12d ago First seen · 50 lines · 33 tokens per session scan A f55beedfd176
challenge is a skill published in the GitHub repository younnieCutler/japan-career-agent (6 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 438 once invoked, about $0.0002 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…
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…
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…