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/jukanntenn/glm-plan-usage/preflightnpx skills add jukanntenn/glm-plan-usage --skill preflightgit clone --depth 1 https://github.com/jukanntenn/glm-plan-usageWrote 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/jukanntenn/glm-plan-usage/preflight)<a href="https://agentmods.dev/skills/jukanntenn/glm-plan-usage/preflight"><img src="https://agentmods.dev/badge/skills/jukanntenn/glm-plan-usage/preflight.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.00104 | $0.00473 |
| Opus 5 | $0.00052 | $0.00236 |
| Sonnet 5 | $0.00021 | $0.00095 |
| Haiku 4.5 | $0.00010 | $0.00047 |
Grade A, and why
preflight 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 5d 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
Generate an end-to-end acceptance manual by diffing the current working tree against the last released version.
Process
- Identify versions — find the latest tag (
git describe --tags --abbrev=0) and confirm the target scope (default: diff from that tag to HEAD). - Gather the full diff —
git diff <tag>..HEADplusgit log --oneline <tag>..HEAD. Read changed source files to understand intent behind each change — not just what lines moved, but what behavior changed for the user. - Classify every change — for each diff, determine: new features, modified behavior, fixed bugs, removed functionality, config changes, and breaking changes.
- Produce the acceptance manual — output a structured checklist organized by functional area (not by file or commit) to a file using output format bellow. For each item include:
- What changed (one-line summary)
- How to verify it (concrete steps: which command to run, what output to expect, which config field to check)
- Edge cases or risks to watch for
Output format
# Preflight Acceptance Manual — <tag> → HEAD
## Summary
<one-paragraph overview of all changes>
## 1. <Functional Area>
- [ ] **<change summary>** — <verification steps>
- [ ] **<change summary>** — <verification steps>
## 2. <Functional Area>
...
Keep the manual concise, actionable, and free of implementation details. Every checklist item must be verifiable by running a command or observing a behavior — no vague items like "verify it works."
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.
- 5d ago First seen · 45 lines · 104 tokens per session scan A 45dc8c4811ef
preflight is a skill published in the GitHub repository jukanntenn/glm-plan-usage (13 stars, last pushed 2mo ago), licensed MIT. It adds 104 tokens to every session and 473 once invoked, about $0.0005 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-30.
Other skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
run-integration-tests
Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.
cli-e2e-testcase-writer
Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
__SKILL_ID__
This fixture verifies that skill content can be written into the target sandbox and queried back immediately.
harness-test-writer
Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…