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 lightweavergit 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/lightweaver)<a href="https://agentmods.dev/skills/hmbown/knightsradiant/lightweaver"><img src="https://agentmods.dev/badge/skills/hmbown/knightsradiant/lightweaver/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/lightweaver"><img src="https://agentmods.dev/badge/skills/hmbown/knightsradiant/lightweaver.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.00020 | $0.00423 |
| Opus 5 | $0.00010 | $0.00211 |
| Sonnet 5 | $0.00004 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
lightweaver 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.
What it actually says
Lightweaver
Make the system legible and honest through names, docs, and API shape.
Invoke when
Follow agents/06-lightweaver/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/06-lightweaver/AGENTS.md. - Use the local order procedures under
agents/06-lightweaver/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 legibility packet defined in agents/06-lightweaver/AGENTS.md.
At minimum, include:
- audience identification (name who reads this surface and what task they are performing — always do this first, before naming anything)
- revised interface or naming description
- one happy-path example
- one failure-path example (audit failure names with the same rigor as success names — error states deserve honest, specific language)
- guarantees/non-guarantees
- suggested simplifications or renames
Do not omit required output items from the canonical output contract, even if you summarize elsewhere.
Hand-off
- Normal: Truthwatcher
- Exception: Elsecaller
Local doctrine
- Order doc:
agents/06-lightweaver/AGENTS.md - Local skill index:
agents/06-lightweaver/skills/SKILL.md
Example invocation
"Use lightweaver 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.
- 8d ago First seen · 60 lines · 20 tokens per session scan A a0af83106932
lightweaver is a skill published in the GitHub repository Hmbown/knightsradiant (2 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 423 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
idea-superpowers-suite
Use when running the full idea workflow: capture a rough idea, expand it into design/UI/implementation docs, research similar products, and generate build-ready Markdown artifacts.
idea-to-implementation-doc
Use when reviewing one specific idea/design doc, researching similar products, and producing a separate technical implementation plan or roadmap.
idea-to-ui-design-brief
Use when turning a product/design doc into a focused UI design brief, optional AI image-generation concept prompts, and implementation-ready UI direction without replacing the main idea workflow.
idea-to-design-doc
Use when turning a rough idea into a focused product/design Markdown doc through guided questions, without moving into implementation too early.
refresh
Use when an existing contextualizer's references may have drifted from current upstream state — typically weekly, or whenever a few days of upstream changes have accumulated — to bring them back into agreement.
using-skill-engine
When the user mentions skill-engine or "the engine" without naming a specific workflow, or wants first-run setup. Inspects .claude/skills/-context/ install state (and any pending -context.proposed/ proposals) across all three install levels, then dispatches to engine-bootstrap when no contextualizer exists, to…