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/devinilabs/pro-skill/audit-reference-originalitynpx skills add devinilabs/pro-skill --skill audit-reference-originalitygit clone --depth 1 https://github.com/devinilabs/pro-skillWrote 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/devinilabs/pro-skill/audit-reference-originality)<a href="https://agentmods.dev/skills/devinilabs/pro-skill/audit-reference-originality"><img src="https://agentmods.dev/badge/skills/devinilabs/pro-skill/audit-reference-originality.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.00085 | $0.01457 |
| Opus 5 | $0.00043 | $0.00728 |
| Sonnet 5 | $0.00017 | $0.00291 |
| Haiku 4.5 | $0.00009 | $0.00146 |
Grade A, and why
audit-reference-originality 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.
This is a copy
100% identical to audit-reference-originality — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Reference Originality
Compare the shipped experience with the complete reference corpus. Treat the audit as an evidence exercise, not a vibe check.
Preserve the audit boundary
- Audit only unless the user also asks for fixes.
- Call findings
originality risks,overlaps, orred flags; do not declare legal plagiarism from visual similarity alone. - Pair every red flag with exact current-site evidence and exact reference evidence.
- Keep fact, inference, and unknown access separate.
- Do not clear a site after checking only its homepage screenshot.
1. Build the source registry
Start with the materials explicitly supplied in the task or recorded by the project:
- manifests, prompt packs, and originality matrices
- representative stills, full-page captures, and section crops
- MP4s and extracted motion frames
- reference URLs and named creators
- source brand assets, copy, numbers, screenshots, and downloads
- project briefs,
IMAGE_CREDITS.md, licenses, and attribution files
Prefer local evidence captured at the time of the brief. Use a live reference only to fill a real gap, because it may have changed. Record each reference's path or URL, role, date when known, and which categories it can prove.
Stop and report an access gap when a promised reference is missing. Do not silently reduce a full-page or motion audit to one cover image.
2. Inventory the current site and its history
Inspect:
- rendered text, metadata, navigation, calls to action, legal copy, and hidden accessible labels
- brand names, wordmarks, logos, icons, people, companies, URLs, and product/interface data
- prices, metrics, dates, counts, percentages, package names, and repeated proof claims
- every rendered image, background, texture, screenshot, font, logo, icon, audio file, and downloadable asset
- every video, poster, frame sequence, shot order, transition, duration, and playback treatment
- layout hierarchy, section order, distinctive compositions, typography behavior, motion grammar, shaders, cursor effects, and interaction sequences
- current source, built output when available, asset provenance, and repository history
What ships with it
3 files 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 · 133 lines · 85 tokens per session scan A 8b8b5e6c6174
audit-reference-originality is a skill published in the GitHub repository devinilabs/pro-skill (20 stars, last pushed 21d ago), licensed MIT. It adds 85 tokens to every session and 1,457 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to audit-reference-originality, differing in 0 lines, and is treated as a copy.
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…