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/michaelycjo/specseal/updatenpx skills add MichaelYcJo/SpecSeal --skill updategit clone --depth 1 https://github.com/MichaelYcJo/SpecSealWrote 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/michaelycjo/specseal/update)<a href="https://agentmods.dev/skills/michaelycjo/specseal/update"><img src="https://agentmods.dev/badge/skills/michaelycjo/specseal/update.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.00030 | $0.01174 |
| Opus 5 | $0.00015 | $0.00587 |
| Sonnet 5 | $0.00006 | $0.00235 |
| Haiku 4.5 | $0.00003 | $0.00117 |
Grade A, and why
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 today.
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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/specseal:update — take the release, and see what is in it
Two commands in a fixed order, and one thing neither of them does: tell you what you are getting. Running them by hand answers "you are now on ", which is a number, not a reason to restart.
Procedure
1. Record what is running. Read the version from
$CLAUDE_PLUGIN_ROOT/.claude-plugin/plugin.json. This is the version this
session actually loaded, which is the one the user is comparing against.
2. Refresh the marketplace, then install.
claude plugin marketplace update specseal
claude plugin update specseal@specseal
Both, in that order. The first pulls the marketplace clone; the second installs from it. Running only the second reports already at the latest version against whatever the clone last knew — the failure is silent and looks like success.
If the second command reports it is already current, say so and stop. There is nothing to restart for.
3. Name what changed. Read CHANGELOG.md from the refreshed marketplace
clone — ~/.claude/plugins/marketplaces/specseal/CHANGELOG.md — and summarize
every entry between the old version and the new one, oldest first. Lead each
with what it changes for the user, not with the release number.
Two kinds deserve to be called out on their own line, because a user who skips them gets surprised later:
- behavior that changes without being asked for — a new gate, a gate that fires where it did not, anything that writes to their tree
- anything they have to do — a path that moved, a setting that was renamed, a compatibility fallback with an expiry
4. Take the preset block if it moved. The markers decide what is safe here.
Everything between <!-- specseal:start --> and <!-- specseal:end --> is
preset-owned and everything outside it is the user's, so replacing the region
cannot touch a line they wrote. install.sh relies on that boundary and so
does preset-setup, which replaces an older block without asking and diffs
only the remainder.
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.
- today Changed a571fcd720c0
- 4d ago First seen · 114 lines · 30 tokens per session scan A 6a666f9788fb
update is a skill published in the GitHub repository MichaelYcJo/SpecSeal (1 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 1,174 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-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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…