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 agentmods add skills/ssbun/csl-agent-kit/alignnpx skills add SSBun/csl-agent-kit --skill aligngit clone --depth 1 https://github.com/SSBun/csl-agent-kitWhat 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 | $0.00050 | $0.00368 |
| Opus 5 | $0.00025 | $0.00184 |
| Sonnet 5 | $0.00010 | $0.00074 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
align 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 2d 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
Align
Re-explain the prior substantive assistant message so the user can verify the reasoning. Re-read sources and re-run checks as needed; do not rely on memory.
Required Output
- Start with a short alignment opener in the user's required response language.
- State the explanation format you chose and why it fits the prior message.
- For each material claim, provide evidence and a
High,Medium, orLowconfidence level. - Include one compact ASCII diagram when it clarifies structure, flow, comparison, or causality.
- Retract or downgrade any earlier claim that cannot be supported.
- End with caveats, low-confidence areas, or next verification steps.
Workflow
- Find the most recent substantive assistant message; skip tool-call-only turns.
- Extract key claims and group them into 2-5 themes when useful.
- Choose a format that fits the content: narrative, table, comparison, flow, timeline, confidence map, or compact clarification.
- Verify each substantive claim against files, command output, docs, or URLs.
- Write with evidence close to the claim.
- Use the diagram only when it improves understanding; skip it for narrowly trivial clarifications.
Reference
Read references/align-method.md for confidence definitions, format-selection rules, diagram patterns, and trivial-clarification criteria.
Principles
- Format follows content.
- Evidence over assertion.
- Honesty over completeness.
- Visuals should clarify, not decorate.
- Keep depth proportional to stakes.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 39 lines · 50 tokens per session scan A d174b9565a08
align is a skill published in the GitHub repository SSBun/csl-agent-kit (10 stars, last pushed 3d ago), licensed MIT. It adds 50 tokens to every session and 368 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…