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 Hmbown/knightsradiant --skill skybreakergit clone --depth 1 https://github.com/Hmbown/knightsradiantWrote 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/hmbown/knightsradiant/skybreaker)<a href="https://agentmods.dev/skills/hmbown/knightsradiant/skybreaker"><img src="https://agentmods.dev/badge/skills/hmbown/knightsradiant/skybreaker/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/hmbown/knightsradiant/skybreaker"><img src="https://agentmods.dev/badge/skills/hmbown/knightsradiant/skybreaker.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.00018 | $0.00384 |
| Opus 5 | $0.00009 | $0.00192 |
| Sonnet 5 | $0.00004 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
skybreaker 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 10d 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
Skybreaker
Turn expectations into enforceable law: lint, types, contracts, CI.
Invoke when
Follow agents/02-skybreaker/AGENTS.md for the canonical decision criteria.
Inputs required
- task statement
- relevant repo or diff context
- current constraints and risk level
- any prior hand-off artifact from the previous order
Procedure
- Read the canonical order doc at
agents/02-skybreaker/AGENTS.md. - Use the local order procedures under
agents/02-skybreaker/skills/. - Keep the work inside this order's stance until its artifact is complete.
- Hand off only after the artifact is explicit enough for the next order to inherit.
Output shape
Produce the full enforcement packet defined in agents/02-skybreaker/AGENTS.md.
At minimum, include:
- invariant statement
- enforcement mechanism chosen
- enforcement lifetime: permanent rule, or sunset rule with expiry condition and removal trigger
- config/code diff summary
- false-positive notes
- rollout severity plan
- exception policy
Do not omit required output items from the canonical output contract, even if you summarize elsewhere.
Hand-off
- Normal: Windrunner
- Exception: Bondsmith
Local doctrine
- Order doc:
agents/02-skybreaker/AGENTS.md - Local skill index:
agents/02-skybreaker/skills/SKILL.md
Example invocation
"Use skybreaker for this task and produce the required artifact before proposing the next order."
Usage rule
Do not combine this with multiple other active order skills unless you are explicitly routing or handing off. One order should own the work at a time.
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.
- 10d ago First seen · 61 lines · 0 tokens per session scan A f25fba1bb32f
skybreaker is a skill published in the GitHub repository Hmbown/knightsradiant (2 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 384 once invoked, about $0.0001 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
e2e-testing-expert
Expert guide for End-to-End (E2E) testing with Playwright, unit/integration testing with Vitest, and CI/CD automated testing pipeline setup / Panduan ahli pengujian End-to-End (E2E) dengan Playwright, pengujian unit/integrasi dengan Vitest, dan otomatisasi CI/CD.
writing-checks
Build the machinery that enforces a convention instead of documenting it — PreToolUse guards that block an action before it runs, CI gates that judge the worktree, selftests that prove a check can turn red, and structural tests that enforce layering. Use this whenever a rule keeps getting violated despite being…
playwright-testing
E2E testing with Playwright - Page Objects, cross-browser, CI/CD.
smoke-test
Launch the app and hands-on verify that it works by interacting with it. Falls back to an existing integration test suite when there is no interactive surface in scope. Use when the user asks to "smoke test", "test it manually", "verify it works", "try it out", "run a smoke test", "check it in the browser", or "does…
exploratory-test
Execute multi-level exploratory testing of the app covering basic functionality, complex operations, adversarial testing, and cross-cutting scenarios, plus usability observations through a UX lens reported separately from defects. Deeper than /smoke-test. Use when the user asks to "exploratory test", "test…
create-test-plan
Analyze what changed and generate a structured test plan at .turbo/test-plans/ .md covering four escalating levels: basic functionality, complex operations, adversarial testing, and cross-cutting scenarios. Use when the user asks to "create a test plan", "plan tests", "what should I test", "generate test scenarios"…