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 lucasviola/specwiki --skill review-pii-redactiongit clone --depth 1 https://github.com/lucasviola/specwikiWrote 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/lucasviola/specwiki/review-pii-redaction)<a href="https://agentmods.dev/skills/lucasviola/specwiki/review-pii-redaction"><img src="https://agentmods.dev/badge/skills/lucasviola/specwiki/review-pii-redaction/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/lucasviola/specwiki/review-pii-redaction"><img src="https://agentmods.dev/badge/skills/lucasviola/specwiki/review-pii-redaction.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.00037 | $0.00414 |
| Opus 5 | $0.00018 | $0.00207 |
| Sonnet 5 | $0.00007 | $0.00083 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
review-pii-redaction 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
Review PII redaction
Parcel Path handles tracking ids, addresses, and recipient hints. Never ship logs or errors that expose them.
What counts as PII here
| Data | OK in user output | Must redact in logs/errors |
|---|---|---|
| Tracking id (short demo id) | Yes (DEMO-1001) |
Redact full tokens in URLs |
| Full tracking URL with token | No | Always redact query params |
| Street address | Truncated city/state only | Never log full address |
| Recipient name | No in verbose mode | Never log |
| Phone / email | Never | Never |
Review steps
- Search the diff for
console.,logger.,verbose, andthrow new Error. - Run verbose locally —
npm run dev -- track --id DEMO-1001 --verboseand scan stdout/stderr. - Check test output — failing tests should not print fixture addresses; use matchers, not snapshot dumps of raw JSON.
- Error paths — carrier failures should say what failed, not paste the raw HTTP body.
Redaction patterns
Prefer helpers over inline string surgery:
// Good
redactTrackingUrl(url); // https://carrier/track/…?token=[REDACTED]
redactAddress(address); // Portland, OR (no street)
// Avoid
console.log("response", rawBody);
PR checklist
- No new unredacted fields in verbose mode
- Error messages safe to paste in a public issue
- Tests mock network; no live responses logged on failure
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 · 47 lines · 37 tokens per session scan A e2f9f52ef237
review-pii-redaction is a skill published in the GitHub repository lucasviola/specwiki (11 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 414 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-30.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…