Borrowing it
Nothing to install: this file belongs to shino369/claude-code-personal-workspace. 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/shino369/claude-code-personal-workspace/main/.claude/skills/security-update/SKILL.mdgit clone --depth 1 https://github.com/shino369/claude-code-personal-workspaceWrote 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/shino369/claude-code-personal-workspace/security-update)<a href="https://agentmods.dev/skills/shino369/claude-code-personal-workspace/security-update"><img src="https://agentmods.dev/badge/skills/shino369/claude-code-personal-workspace/security-update/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/shino369/claude-code-personal-workspace/security-update"><img src="https://agentmods.dev/badge/skills/shino369/claude-code-personal-workspace/security-update.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.00068 | $0.02637 |
| Opus 5.5 | $0.00027 | $0.01055 |
| Sonnet 5.5 | $0.00014 | $0.00527 |
| Haiku 4.5 | $0.00007 | $0.00264 |
Grade A, and why
security-update 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 10d 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Update
Workflow
1. Identify Vulnerable Package
Run the audit and note the vulnerable package name, version range, which direct dependency pulls it in, and the recommended safe version:
pnpm audit
2. Check Safe Version Age (minimumReleaseAge)
Before applying any fix, verify the target version was published > 10,080 minutes ago (7 days). This guards against package hijacking / dependency confusion attacks.
Two enforcement layers exist.
pnpm-workspace.yamlalready setsminimumReleaseAge: 10080, sopnpm installitself refuses to resolve any package version younger than 7 days. The script below is a complementary pre-check that gives a human-readable age report before you write anything to the workspace file. Keep both: the script stops you writing a too-new version; the workspace setting stops you installing one. Note thatpnpm audit --fix(Step 4a) can punch a hole in this by appending tominimumReleaseAgeExclude— see Step 4a.
node .claude/skills/security-update/scripts/check_release_age.mjs <package-name> <target-version>
Do not proceed if the version is younger than 10,080 minutes. Pick the next older safe version that still resolves the vulnerability.
3. Try Direct Parent Upgrade First
Always attempt this before adding an override. Upgrading the parent is cleaner and avoids override sprawl.
a. Find which direct dependency pulls in the vulnerable package:
pnpm why <vulnerable-package>
b. Check the current and latest version of the parent:
pnpm outdated <parent-package>
c. Choose the target parent version and verify its age before editing the catalog:
node .claude/skills/security-update/scripts/check_release_age.mjs <parent-package> <target-parent-version>
Do not update the catalog if the parent version is younger than 10,080 minutes. Pick an older safe parent version, or use Step 4 if no aged parent version resolves the vulnerability.
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.
- 10d ago First seen · 219 lines · 68 tokens per session scan A 37c1a7816189
security-update is a skill published in the GitHub repository shino369/claude-code-personal-workspace (3 stars, last pushed 11d ago), licensed ISC. It adds 68 tokens to every session and 2,637 once invoked, about $0.0003 per session on Opus 5.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-10-18.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…