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 JasonColapietro/suede-creator-skills --skill suede-parity-contractgit clone --depth 1 https://github.com/JasonColapietro/suede-creator-skillsWrote 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/jasoncolapietro/suede-creator-skills/suede-parity-contract)<a href="https://agentmods.dev/skills/jasoncolapietro/suede-creator-skills/suede-parity-contract"><img src="https://agentmods.dev/badge/skills/jasoncolapietro/suede-creator-skills/suede-parity-contract/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/jasoncolapietro/suede-creator-skills/suede-parity-contract"><img src="https://agentmods.dev/badge/skills/jasoncolapietro/suede-creator-skills/suede-parity-contract.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00212 | $0.01872 |
| Opus 5 | $0.00106 | $0.00936 |
| Sonnet 5 | $0.00042 | $0.00374 |
| Haiku 4.5 | $0.00021 | $0.00187 |
Grade A, and why
suede-parity-contract 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 6d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Suede Parity Contract
Iron Law: generate the contract from the reference surface's live constants.
A contract you transcribe is a second copy, and second copies drift.
A contract you generate cannot disagree with the code it came from.
Silent drift is the failure this prevents. Nothing crashes when a threshold is copied wrong into a second language. The two surfaces simply start answering the same question differently, and a user finds out before you do.
Step 1 — Name one reference surface
Exactly one surface is the reference. Every other surface is a follower that asserts against it. Two references is two sources of truth with extra steps.
Pick the surface where the domain is most complete and most exercised, and write
that choice into the contract's reference field so nobody re-litigates it.
Step 2 — Build the contract by importing, never retyping
The builder imports the constants from the modules the application actually runs on and serializes them. Retyping a value into the builder reintroduces exactly the copy this skill exists to delete.
When a needed value is private, export it rather than duplicating it. That is a one-line change and it keeps the count of definitions at one.
Serialize with stable key order and a trailing newline, because followers vendor the file verbatim and a reformat shows up as a spurious diff.
Step 3 — Make staleness fail on the reference side
One test rebuilds the contract in memory and compares it to the committed file. Without it the JSON is a snapshot someone took once.
Give it a write mode so regeneration is one command, and put that command in the
contract's README and in the file's own note field:
CONTRACT_WRITE=1 <test runner> <contract test>
Compare parsed objects first so the failure names the key that moved, then compare raw bytes so a reformat is caught too.
Step 4 — Vendor byte-identical to each follower
Followers keep a copy at the same relative path. Prove it matches rather than assuming:
What ships with it
2 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.
- 6d ago First seen · 178 lines · 212 tokens per session scan A a5ed916b84a6
suede-parity-contract is a skill published in the GitHub repository JasonColapietro/suede-creator-skills (135 stars, last pushed today), licensed MIT. It adds 212 tokens to every session and 1,872 once invoked, about $0.0011 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-06.
Other skills, from other repositories
api-test
Run API integration tests against the running backend, verify endpoints return expected responses and status codes. Use after deploying a preview or starting the dev server.
deploy-preview
Build Docker images and launch a local preview environment with docker-compose. Use to test the full stack locally before merging.
build-and-test
Install dependencies, run type checking, lint, tests, and build the project. Use after making code changes to verify nothing is broken.
qa-testing
Run QA testing on a page, feature, or full site at one of three depth tiers (smoke, standard, full). Use this skill whenever the user asks to QA a page or site, run a smoke test after a deploy, verify a page before launch, or run a regression sweep. Triggers on QA, QA sweep, smoke test, regression test, post-deploy…
visual-qa
Runs rigorous visual QA across web, terminal, and paginated surfaces with screenshot evidence and a verdict. Use for any UI build or change, or when asked whether a page, component, or TUI looks right.
remove-ai-slops
Removes AI-generated code smells from branch changes or an explicit file list behind regression tests. Use when the user asks to clean up, deslop, or remove AI-slop patterns from recent changes.