Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add MichaelYcJo/SpecSeal/plugin install 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/config)<a href="https://agentmods.dev/skills/michaelycjo/specseal/config"><img src="https://agentmods.dev/badge/skills/michaelycjo/specseal/config.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.1 | $0.00042 | $0.01225 |
| Opus 5 | $0.00021 | $0.00613 |
| Sonnet 5 | $0.00008 | $0.00245 |
| Haiku 4.5 | $0.00004 | $0.00122 |
Grade A, and why
config 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 2d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/specseal:config — what this repository decided, and how to decide otherwise
seal/config.md holds what a repository says about itself. Every row has a
default, an absent row is not an error, and until now the only way to see any
of it was to open a file nobody has a reason to open.
First setup asks its questions once and never again. This is how to ask them later.
Where the file is
<repo>/seal/config.md where that directory exists, and
$(git rev-parse --git-common-dir)/seal/config.md otherwise — local mode,
where the root sits under the common git directory. Resolve it that way rather
than spelling the first place and stopping.
No root at either place means this repository has not been set up. Say so,
name the implement skill's bootstrap as what does it, and stop. Do not
create the file: its presence at one of those two places is what opts a
repository in, and creating it here would opt somebody in from a command they
ran to look.
Procedure
1. Show every row, present or not. Read the file, and print all three with their current values — including the ones the file does not carry, with the default and where it comes from. A row a repository never set is the most likely one somebody wants to change, and showing only what is present hides exactly those.
| Row | Default | What it governs |
|---|---|---|
Commit and pull request language |
English | the commit subject and body, the pull request title and body, and a review report posted as a pull-request comment |
Record language |
English | the prose in spec.md, plan.md, overview.md, questions.md, changelog.md, a round record's cells, and a ledger row's claim and grounds |
Mode |
the folder decides | which of the two places the root should live at |
Every way of not naming a language lands on English — no file, no such row, an empty value, a file that does not parse. Say the default and the reason rather than showing a blank.
2. For the mode, show what is true as well as what is written. That row is
what the repository wants; the folder's location is what it has, and the
two are separate on purpose. Run seal mode and report what it says — the
folder, the row, and whether they agree. Do not read the row yourself for this
one: seal mode is what the pull-request checks run, and a second reader is a
second answer.
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.
- 2d ago First seen · 98 lines · 42 tokens per session scan A c1743cbc8844
config is a skill published in the GitHub repository MichaelYcJo/SpecSeal (1 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 1,225 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-09-04.
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…
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…
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…