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 hariharapanigrahy/layerkit --skill layerkit-deletion-firstgit clone --depth 1 https://github.com/hariharapanigrahy/layerkitWrote 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/hariharapanigrahy/layerkit/layerkit-deletion-first)<a href="https://agentmods.dev/skills/hariharapanigrahy/layerkit/layerkit-deletion-first"><img src="https://agentmods.dev/badge/skills/hariharapanigrahy/layerkit/layerkit-deletion-first/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/hariharapanigrahy/layerkit/layerkit-deletion-first"><img src="https://agentmods.dev/badge/skills/hariharapanigrahy/layerkit/layerkit-deletion-first.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.00053 | $0.00559 |
| Opus 5.5 | $0.00021 | $0.00224 |
| Sonnet 5.5 | $0.00011 | $0.00112 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
layerkit-deletion-first 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 1mo 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
layerkit-deletion-first
Use this skill before implementation work, especially before layerkit-source-edit-client edits production datalayer code.
Before adding code, identify existing code, docs, tests, fixtures, and package surfaces that can be removed or rewritten.
Before a large deletion/rewrite or strategic redirect, prove the new direction with one small passing gate: an eval, end-to-end QA check, contract-heal case, or before/after acceptance test.
Protocol
- Identify existing code, docs, tests, fixtures, scripts, exports, commands, and shims that can be removed or rewritten.
- Prefer modifying or deleting existing code over adding files.
- Do not add a new abstraction until the existing abstraction has been inspected and cannot reasonably change.
- For every new file, function, export, command, fixture, or skill, state what it replaces.
- If it replaces nothing, justify why the expansion is necessary.
- Target net-negative or near-neutral LOC unless functionality truly expands.
- Before a strategic redirect or large deletion/rewrite, define what must pass, the proof artifact, and the fallback if validation fails; record the proof step before continuing.
- Keep tests proportional to the implementation size; release hardening must cover client-package edit paths, mapping semantics, deletion-first behavior, and CI/eval gates touched by the change.
Deletion Pass
Check these surfaces before adding:
- stale demos, design notes, launch scripts, sample-only assets
- legacy wrappers and compatibility aliases not required by public API
- tests for removed behavior
- duplicated command paths or old workflow names
- unused exports, fixtures, scripts, generated output, and package contents
- docs that describe non-current product paths
For heal/integration work, preserve only the spine:
API spec/doc -> contract drift -> map/proposal update -> privacy/checker -> production datalayer integration -> client package verification
Move required examples into evals/fixtures; delete demo/docs packaging around them.
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.
- 1mo ago First seen · 53 lines · 53 tokens per session scan A edbb104bb4ef
layerkit-deletion-first is a skill published in the GitHub repository hariharapanigrahy/layerkit (8 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 559 once invoked, about $0.0002 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
competitive-teardown
Systematic competitor analysis covering product teardowns, 12-dimension scoring rubric, feature comparison matrices, SWOT analysis, pricing model deconstruction, UX audits, and strategic action plans with stakeholder presentation templates.
contract-and-proposal-writer
Generate business documents — contracts, proposals, SOWs, NDAs, MSAs — with jurisdiction-aware clauses for US, EU, UK, and DACH. Use when starting client engagements, writing proposals, drafting agreements, or needing GDPR-compliant DPAs.
deal-desk
Deal desk: reviews, approves, and structures non-standard sales deals. Use when standing up a deal desk, building approval-threshold matrices, designing deal-review packets, routing deals, or auditing deals for compliance.
form-cro
Form optimization for lead capture, contact, demo request, application, and checkout forms. Covers field-cost analysis, multi-step form design, validation UX, mobile optimization, and A/B testing frameworks.
free-tool-strategy
Free tool marketing strategy covering idea evaluation, tool design, lead capture architecture, SEO landing pages, launch playbook, and ROI measurement for calculators, generators, checkers, graders, and interactive tools.
popup-cro
Popup and modal optimization for conversion. Covers exit-intent, slide-ins, banners, timing optimization, frequency capping, audience targeting, compliance, and A/B testing frameworks for lead capture, promotions, and announcements.