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 dkadts/landing-kit-building --skill auditgit clone --depth 1 https://github.com/dkadts/landing-kit-buildingWrote 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/dkadts/landing-kit-building/audit)<a href="https://agentmods.dev/skills/dkadts/landing-kit-building/audit"><img src="https://agentmods.dev/badge/skills/dkadts/landing-kit-building/audit.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.00051 | $0.02660 |
| Opus 5 | $0.00026 | $0.01330 |
| Sonnet 5 | $0.00010 | $0.00532 |
| Haiku 4.5 | $0.00005 | $0.00266 |
Grade A, and why
audit 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 8d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/audit
Final verifier before /deploy. Categories: anti-slop (what killed prior projects), technique (perf, a11y, SEO), contract (matches DESIGN-LOCK, brief, and the approved manifest).
When to use
- After
/build+/mobile(site assembled). - Before
/deploy(required gate). - Regularly during development for sanity checks.
Check categories
A. Anti-AI-slop (DESIGN-LOCK enforcement)
Walk HTML/CSS/JS. Each check = pass / fail with file/line.
- Emoji in HTML — grep
[\u{1F300}-\u{1F9FF}]in HTML. Fail if found (unless emoji is in the brand book). - More than one gradient — grep
linear-gradient|radial-gradient|conic-gradient. Fail if > 1 unique. - More than one radius — grep all
border-radius:. Everything must bevar(--radius). Fail on hardcode. - More than 2 font-weights — grep
font-weight:. Fail if > 2 unique values project-wide. - Center-align > 50% — count sections with
text-align: centervs total. Warning if > 50%. - More than 5 section types — count unique
<section class="sec sec-...">. Fail if > 5 (see DESIGN-LOCK §8). - Decorative icons — visually check: icons purely for decoration? Warning.
- Bounce/spring motion — grep
cubic-bezierfor out-of-range values (>1 or <0). Fail if found and not allowed in DESIGN-LOCK. - Mixed icon libraries — > 1 SVG sprite or > 1 icon font. Fail.
- Pill everywhere — if DESIGN-LOCK radius ≠ 999 but
border-radius: 999pxpresent — Fail.
A2. Typography (English print-quality rules)
- Hanging short words at line end — grep the rendered HTML for space-separated short words at potential line breaks. Specifically: scan each text node for space-terminated sequences ending in words from the
/typographycanonical short-word list (a,an,the,and,or,but,of,to,in,on,for,with,is,are,be,it,we,you, etc.). If the space is a regular space (not ) and the next word exists, this is a violation. Fail with line reference. - Dashes at line end — grep for
[-–—](space, dash, space). If the space before the dash is a regular space (not ), this is a violation. Fail. - Orphans in headings and paragraphs — for each
<h1>,<h2>,<h3>,<p>,<li>,<blockquote>, verify the last two words are joined by . Fail if a regular space separates the last two words of a text node. - Language contract — if
<html lang="en">is not set, and the copy is English, fail the language attribute check (also caught in D). Typography rules only apply to English. -
no-typoopt-outs — count elements withclass="no-typo". Warning if > 3 (user disabled typography on many blocks — worth reviewing).
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.
- 8d ago First seen · 169 lines · 51 tokens per session scan A 5e0654c78ff5
audit is a skill published in the GitHub repository dkadts/landing-kit-building (2 stars, last pushed 19d ago), licensed MIT. It adds 51 tokens to every session and 2,660 once invoked, about $0.0003 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-31.
Other skills, from other repositories
verify
Build, launch, and drive the AppointMe stack to verify a change end-to-end at its runtime surface.
eval-grader
Measure output quality, don't vibe it: score a generative task with a two-layer grader — deterministic code metrics + per-dimension LLM-as-judge — over a fixed task set, as signed deltas vs a pinned baseline. Grades cost alongside correctness (pass-slow).
iterate
Refine-to-Done loop: repeat until tests green + review clean + nothing deferred; bounded. Not the harness /loop.
testing
The how of testing: pyramid, AAA, isolation, risk coverage, determinism. Guarantees the DoD's "tests are green". test-expert-csk applies it. Use when writing or changing tests, or when a suite is flaky, slow or green for the wrong reason.
ci-pipeline
CI pipeline discipline: lint→build→test→quality→security, fail-fast, deterministic build, secret handling, PR gates.
yellow-sheet-corpus
Run the Yellow Sheet chain end to end against ANY matter, from the original PDFs, and read the result honestly. Use whenever someone asks what has been tested end to end, whether a matter produces a usable sheet, how to onboard a NEW matter, or asks to re-run after a code change. Carries the intake mechanism that…