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 freezingfunky/ashwin-skills --skill render-checkgit clone --depth 1 https://github.com/freezingfunky/ashwin-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/freezingfunky/ashwin-skills/render-check)<a href="https://agentmods.dev/skills/freezingfunky/ashwin-skills/render-check"><img src="https://agentmods.dev/badge/skills/freezingfunky/ashwin-skills/render-check/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/freezingfunky/ashwin-skills/render-check"><img src="https://agentmods.dev/badge/skills/freezingfunky/ashwin-skills/render-check.svg" alt="Reviewed on agentmods" width="80" 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.00086 | $0.01322 |
| Opus 5.5 | $0.00034 | $0.00529 |
| Sonnet 5.5 | $0.00017 | $0.00264 |
| Haiku 4.5 | $0.00009 | $0.00132 |
Grade A, and why
render-check 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Render Check
The source file is not the truth. The served markup + compiled CSS are the truth.
Why this skill exists
AI agents love to say "done" after editing a React/Tailwind file. Sometimes the source changed but the browser is still serving a stale build (Next.js Fast Refresh quietly stopped updating). Typecheck passes. Curl returns 200. The screen doesn't change.
Iron rule: do not tell the user a visual change is done until the served HTML contains the new markup AND the served CSS contains the new rule. "I edited the file and tsc passes" is not evidence the change rendered.
Discover project specifics first
Do not hardcode ports or paths. Before checking:
- Find how this repo starts the dev server (package.json scripts, README, CLAUDE.md).
- Note the port and the route under test.
- Note the build-cache dir (often
.next/for Next.js;.vite//dist/for Vite). - Find the served CSS link from the HTML — don't invent the path.
Protocol (run before confirming a frontend change)
1. Make sure the server is alive and freshly compiled
# Replace PORT with the project's dev port
lsof -ti :PORT >/dev/null 2>&1 && echo "up" || echo "down"
If the change touched layout/Tailwind and the result looks unchanged, assume staleness first — restart clean rather than re-editing CSS:
lsof -ti :PORT | xargs kill -9 2>/dev/null
rm -rf .next # or this project's cache dir
# restart via the project's usual dev command (background)
until curl -fsS -o /dev/null "http://localhost:PORT/<route>"; do sleep 2; done
2. Confirm the new MARKUP is in the served HTML
Grep the live page for the exact classes/attributes/text you just added:
URL="http://localhost:PORT/<route>"
curl -sS "$URL" --max-time 30 | grep -c "<the new class or text>"
0 = the change did not render. Stop. Restart the server (step 1). Re-check. Do NOT keep
editing source — the source may already be correct.
Grep gotcha — interpolation markers: React may insert <!-- --> around {interpolations},
so a substring that straddles a dynamic value won't match raw HTML. Grep a purely-static
substring, or strip tags first:
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 · 132 lines · 86 tokens per session scan E 80e310f6d025
render-check is a skill published in the GitHub repository freezingfunky/ashwin-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 86 tokens to every session and 1,322 once invoked, about $0.0003 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-31.
Other skills, from other repositories
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
writing-livekit-scenarios
Creates and maintains the scenarios a LiveKit agent simulation runs, and wires the agent to consume them. Use when the user asks "what should I test", "generate simulation scenarios", "write scenarios for my agent", "add a scenario for X", "organize my scenario files", "my simulations are flaky", "the scenario hits my…
running-livekit-simulations
Runs LiveKit agent simulations and acts on the results. Use when the user says "run my simulations", "regression test my agent before deploying", "run the scenarios", "use lk agent simulate", "did my agent pass", "why did this scenario fail", "run simulations in CI", "test the audio pipeline", "check turn-taking and…
dsh-error-handling
A workflow for designing and reviewing how software reports errors, partial success, unknown results, recovery, retries, cancellation, and failure feedback.
dsh-pre-push-checks
A delivery-readiness check for software changes before they are pushed or released. It compares required checks with the actual source, build output, tests, and user-facing behavior.