Borrowing it
Nothing to install: this file belongs to Zetetic-Dhruv/witness-mcp. 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/Zetetic-Dhruv/witness-mcp/main/.claude/skills/make-nontrivial/SKILL.mdgit clone --depth 1 https://github.com/Zetetic-Dhruv/witness-mcpWrote 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/zetetic-dhruv/witness-mcp/make-nontrivial)<a href="https://agentmods.dev/skills/zetetic-dhruv/witness-mcp/make-nontrivial"><img src="https://agentmods.dev/badge/skills/zetetic-dhruv/witness-mcp/make-nontrivial/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/zetetic-dhruv/witness-mcp/make-nontrivial"><img src="https://agentmods.dev/badge/skills/zetetic-dhruv/witness-mcp/make-nontrivial.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.00089 | $0.00493 |
| Opus 5 | $0.00044 | $0.00246 |
| Sonnet 5 | $0.00018 | $0.00099 |
| Haiku 4.5 | $0.00009 | $0.00049 |
Grade A, and why
make-nontrivial 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 11d 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
make-nontrivial
A trivial application restates the CV in the form's grammar — the axis an ATS reduces to keywords. A non-trivial one changes what the reader thinks they're hiring for. Produce four parts:
- Reframe — the role's REAL problem, then the new axis where this candidate is the obvious hire
(their differentiators from
profile.json→positioning), not years/title/keywords. - Why-us — 90–130 words: one concrete observation about the company's product + their edge + one real proof point.
- Teardown (the witness) — a short teardown of THE COMPANY'S product through the candidate's lens: where intended meaning may diverge from how users interpret it, one testable hypothesis, how they'd measure it. Hypotheses only — never invent facts about the company.
- Proof map + risks — every claim maps to a real fact in
profile.json(else markneeds_confirmationand ask — never fabricate). Then 1–2 honest lines on what a skeptic will doubt.
How
- Pre-authored kits (if any) live in
<folder>/nontrivial_kits.jsonand auto-attach in apply-to-job. - New company:
python -m src.cli --data-dir <folder> kit --company "<Name>" --role "<Role>" --context "<what you know>"(needsANTHROPIC_API_KEY). Without a key, draft it yourself following the four parts. - Sanity-check any answer:
python -m src.cli triviality --text "<answer>" --company "<Name>". If TRIVIAL, add a company-specific reframe + a real proof point.
Non-trivial ≠ inflated — the proof-map honesty gate keeps repositioning grounded. No clichés, no em dashes.
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.
- 11d ago First seen · 28 lines · 89 tokens per session scan A d417e9eb3039
make-nontrivial is a skill published in the GitHub repository Zetetic-Dhruv/witness-mcp (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 89 tokens to every session and 493 once invoked, about $0.0004 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…