Borrowing it
Nothing to install: this file belongs to gridaco/nothing. 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/gridaco/nothing/main/.agents/skills/dev-render-htmlcss-svg-feature/SKILL.mdgit clone --depth 1 https://github.com/gridaco/nothingWrote 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/gridaco/nothing/dev-render-htmlcss-svg-feature)<a href="https://agentmods.dev/skills/gridaco/nothing/dev-render-htmlcss-svg-feature"><img src="https://agentmods.dev/badge/skills/gridaco/nothing/dev-render-htmlcss-svg-feature/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/gridaco/nothing/dev-render-htmlcss-svg-feature"><img src="https://agentmods.dev/badge/skills/gridaco/nothing/dev-render-htmlcss-svg-feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 331 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Agent Snooping · line 460 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Prompt Injection · line 501 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 507 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00094 | $0.05636 |
| Opus 5.5 | $0.00038 | $0.02254 |
| Sonnet 5.5 | $0.00019 | $0.01127 |
| Haiku 4.5 | $0.00009 | $0.00564 |
Grade A, and why
dev-render-htmlcss-svg-feature 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 2mo 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 — 512 lines — stays where its author put it; the contents beside it link to each section on GitHub.
grida-htmlcss::svg — feature loop
Status (2026-07-24): the target module is a frozen donor. Per D-N, the SVG engine of record, no new behavior lands in
htmlcss::svg; SVG capability evolves as rungs on the engine of record (websem → rframe → n0), Chromium-baked underfixtures/web-first/. Use this loop only for owner-directed wire-back or donor study — not for new feature work.
What this is. A heavy, manually-invoked loop for driving a single
SVG feature forward in crates/htmlcss/src/svg/. Do not
auto-trigger; load only when the user explicitly runs it.
Sister skill. dev-render-htmlcss-feature
covers the HTML/CSS path (different code surface, different fixture
suite, single oracle). This SKILL covers the SVG path: same five-phase
shape, but different corpus and different scoring policy.
| Aspect | HTML/CSS sister skill | This (SVG) skill |
|---|---|---|
| Renderer module | crates/htmlcss/src/ (excl. svg/) |
crates/htmlcss/src/svg/ |
| Corpus | fixtures/test-html/L0/ (we author) |
fixtures/local/resvg-test-suite/ (vendored, 1679 fixtures) |
| Oracle | Playwright Chromium (refbrowser, on-the-fly) | expected.png (suite author) + baked Chrome PNG |
| Scoring | Single oracle, gate=L0.exact floor 1.0 |
Multi-oracle: consensus / disputed / UB; gate = consensus pass-rate |
| Tooling | cargo run -p grida_wpt -- render --suite … |
cargo run -p grida_dev -- reftest <run|bake|inspect|summary> |
Why multi-oracle (read this before phase 1)
The resvg-test-suite ships one expected.png per fixture — but that
PNG is the suite author's read of the spec, not a browser
oracle. For ~12% of fixtures Chrome diverges from expected.png
(disputed) and ~4% have no defined behavior at all (UB). The harness
ingests the suite's results.csv (a 9-renderer status matrix) to
classify each fixture:
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.
- 2mo ago First seen · 512 lines · 94 tokens per session scan A a250bb643164
dev-render-htmlcss-svg-feature is a skill published in the GitHub repository gridaco/nothing (54 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 94 tokens to every session and 5,636 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
spec-driven-tests
Rebuild a package's unit test suite around a behavior specification (SPEC.md) derived from the implementation, with every test citing a numbered rule ID. Use when asked to do a spec-driven test rebuild, write a SPEC.md for a package, repeat the state or store spec process (PRs.
write-e2e-tests
Writing Playwright E2E tests for tldraw. Use when creating browser tests, testing UI interactions, or adding E2E coverage in apps/examples/e2e or apps/dotcom/client/e2e.
write-unit-tests
Writing unit and integration tests for the tldraw SDK. Use when creating new tests, adding test coverage, or fixing failing tests in packages/editor or packages/tldraw. Covers Vitest patterns, TestEditor usage, and test file organization.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.