Borrowing it
Nothing to install: this file belongs to gcake119/joplin-llm-wiki. 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/gcake119/joplin-llm-wiki/main/.cursor/skills/spectra-audit/SKILL.mdgit clone --depth 1 https://github.com/gcake119/joplin-llm-wikiWrote 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/gcake119/joplin-llm-wiki/spectra-audit)<a href="https://agentmods.dev/skills/gcake119/joplin-llm-wiki/spectra-audit"><img src="https://agentmods.dev/badge/skills/gcake119/joplin-llm-wiki/spectra-audit/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/gcake119/joplin-llm-wiki/spectra-audit"><img src="https://agentmods.dev/badge/skills/gcake119/joplin-llm-wiki/spectra-audit.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.00022 | $0.02027 |
| Opus 5 | $0.00011 | $0.01014 |
| Sonnet 5 | $0.00004 | $0.00405 |
| Haiku 4.5 | $0.00002 | $0.00203 |
Grade A, and why
spectra-audit 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.
This is a copy
100% identical to spectra-audit — 8 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit changed code for security sharp edges — API design traps, dangerous defaults, and interfaces that make it easy to do the wrong thing.
Good APIs don't require developers to "be careful" to stay secure. If the correct usage requires reading docs, remembering rules, or understanding cryptography, the API has failed.
Core principle: Security should be the path of least resistance. Insecure usage should be harder than secure usage.
Two Modes
This skill operates in two modes depending on how it's invoked:
- Standalone (
/spectra:audit): Full 3-agent parallel analysis on current git diff. See Standalone Mode. - Discipline (via
/spectra:applywhenaudit: true): Condensed checklist applied during implementation. See Discipline Mode.
Both modes share the same Core Framework.
Standalone Mode
When invoked directly as /spectra:audit:
Phase 1: Gather Changes
Run git diff HEAD to get the full diff of current modifications.
If there are no changes, report "No changes to audit" and stop.
Phase 2: Parallel 3-Agent Analysis
Launch 3 agents in parallel (one message, 3 tool calls). Each agent receives the full diff and analyzes it through one adversary lens.
Agent 1 — The Scoundrel (壞蛋)
A malicious developer or attacker deliberately manipulating configuration.
Search the diff for:
- Config options that can disable security mechanisms
- Algorithm parameters that accept downgrades (e.g.,
"none","md5") - Values that can be injected to bypass validation
- Dangerous config combinations (e.g.,
auth_required: true+bypass_auth_for_health: true+health_check_path: "/") - String concatenation in security-critical paths (permissions, queries, paths)
Agent 2 — The Lazy Developer (懶惰的開發者)
A developer who copy-pastes examples and skips documentation.
Search the diff for:
- Unsafe defaults:
verify: false,timeout: 0, empty strings as keys - Zero/nil/empty behavior: what does
timeout=0,max_attempts=0,key=""mean? - Error messages that don't guide toward secure usage
- The "first example found" test: is the most obvious usage secure?
- Path of least resistance: does the simplest way to use this API produce secure results?
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 · 235 lines · 22 tokens per session scan A e9e639322f6f
spectra-audit is a skill published in the GitHub repository gcake119/joplin-llm-wiki (2 stars, last pushed 3mo ago), licensed MIT. It adds 22 tokens to every session and 2,027 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to spectra-audit, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
api-linter
MCP definition linter rules reference. Use when bun run lint:mcp or bun run devcheck reports a lint error or warning (format-parity, schema-is-object, name-format, server-json-, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
code-simplifier
Post-session code review and cleanup against a working tree of changes. Analyzes git diff to simplify, consolidate, and align changed code with the existing codebase — modernize syntax, remove unnecessary complexity, consolidate duplicated logic, catch efficiency issues. Use after a substantive working session, or…
patent-precheck
Score code for patentability with Patent PreCheck. Use when the user asks "can this be patented?", wants a patentability/novelty/§101/§102/§103 check, or wants to know if an invention or codebase is filing-ready.
Receiving Code Review
Guidelines for analyzing and applying peer code review feedback objectively.
Requesting Code Review
Preparing PR summaries, diff highlights, and verification proof for peer review.