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 osovv/grace-marketplace --skill grace-refactorgit clone --depth 1 https://github.com/osovv/grace-marketplaceWrote 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/osovv/grace-marketplace/grace-refactor)<a href="https://agentmods.dev/skills/osovv/grace-marketplace/grace-refactor"><img src="https://agentmods.dev/badge/skills/osovv/grace-marketplace/grace-refactor/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/osovv/grace-marketplace/grace-refactor"><img src="https://agentmods.dev/badge/skills/osovv/grace-marketplace/grace-refactor.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.00031 | $0.00209 |
| Opus 5 | $0.00015 | $0.00105 |
| Sonnet 5 | $0.00006 | $0.00042 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
grace-refactor 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 11d 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
<must_do>
- Resolve affected
M-*,DF-*, andV-M-*anchors through.grace/graph/index.xmland.grace/verification/index.xml. - Check active
.grace/changesfor scope overlap before editing. - Preserve or update file-local
LINKS:, module contracts, function contracts, and semantic blocks. - Update durable graph and verification artifacts only when the refactor intentionally changes boundaries, paths, or evidence.
- Run targeted tests and
grace lint --path <project-root>when available. </must_do>
What ships with it
1 file 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.
- 11d ago First seen · 19 lines · 31 tokens per session scan A 0790c92e84ae
grace-refactor is a skill published in the GitHub repository osovv/grace-marketplace (240 stars, last pushed 7d ago), licensed MIT. It adds 31 tokens to every session and 209 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
audit-artifact
Interactive workflow for auditing a SpecRoute artifact before it is treated as implementation-ready. Use when checking a PRD, spec triplet, prompt set, agent file, skill, command, hook, rule, or runtime layout. Asks which artifact path to inspect and which contract to apply. Triggers - "audit this artifact", "check…
coding-standards
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development. Use when writing any code to ensure consistent quality.
migration-review
Review database migration files when a change adds or modifies paths under migrations/. Use it before merge to collect forward, rollback, locking, and data-safety evidence.
code-review-excellence
This skill should be used when the user asks to review a diff or pull request, write review comments, audit code quality, establish review standards, or improve how a team performs code review.
link-check
Verify @file references in AIWG skills and agents against the linking contract — per-file or corpus-wide, with optional auto-fix.
git-pr-review
A read-only reviewer for GitHub pull requests, which are proposed code changes submitted for review. It produces an evidence-based report about whether a pull request should be merged.