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/jl-cmd/claude-dev-env/cert-classification-rulenpx skills add jl-cmd/claude-dev-env --skill cert-classification-rulegit clone --depth 1 https://github.com/jl-cmd/claude-dev-envWrote 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/jl-cmd/claude-dev-env/cert-classification-rule)<a href="https://agentmods.dev/skills/jl-cmd/claude-dev-env/cert-classification-rule"><img src="https://agentmods.dev/badge/skills/jl-cmd/claude-dev-env/cert-classification-rule.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 | $0.00091 | $0.02938 |
| Opus 5 | $0.00046 | $0.01469 |
| Sonnet 5 | $0.00018 | $0.00588 |
| Haiku 4.5 | $0.00009 | $0.00294 |
Grade A, and why
cert-classification-rule 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 4d 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cert-Failure Classification Rule
Add or change how a Samsung Galaxy Store certification rejection is sorted into one of four
buckets: Fold, unfixable, mixed, or fixable. A rejection lands in a bucket from its
must-fix issue titles plus a Fold device check, and the bucket decides which subfolder holds
the theme folder.
Contents
- When to use
- Procedure checklist
- The classification model
- How to add an unfixable title pattern
- How to add the paired production-path test
- Re-sort already-filed folders for a day
- Gotchas
- File index
- Folder map
When to use
Use this skill when the user asks to:
- add a fixable item, add an unfixable item, or add a mixed item
- mark a rejection unfixable, or classify a cert rejection
- add a cert rule
Almost every such request is one new unfixable title pattern plus its paired test. The
fixable and mixed buckets are not configured by hand (see the model below), so a request
to "add a fixable item" usually means "stop treating this title as unfixable" or "confirm
this title stays fixable with a guard test".
When a title pattern cannot help
If the rejection's only unfixable cue lives in the report description (the L_TESTRESULT
text, for example *Not Identifiable) and no must-fix title carries it, stop and tell the
user this exact point:
This rejection's only unfixable signal is in the report description, not a must-fix title. The classifier reads titles only, so no pattern here will catch it — teaching it to read the description is a code change to the classifier, not a config rule.
Procedure checklist
Copy this and check each item off as you go:
- Confirm the unfixable cue is in a must-fix title, not only the description (see Gotchas).
- Append the new
{pattern, label, review_note}after the Gallery entry inunfixable_patterns.json. - Add a paired production-path test: the live title classifies as
unfixable, plus a negative guard for an out-of-scope title. - Run the tests from the
shared_utilsdirectory and confirm green. - Re-sort the affected day folders with the re-sort recipe (dry run first, then
--apply).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 225 lines · 91 tokens per session scan A 7a40bae5452c
cert-classification-rule is a skill published in the GitHub repository jl-cmd/claude-dev-env (5 stars, last pushed today), licensed MIT. It adds 91 tokens to every session and 2,938 once invoked, about $0.0005 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…