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/microsoft/wassette/copyright-headersnpx skills add microsoft/wassette --skill copyright-headersgit clone --depth 1 https://github.com/microsoft/wassetteWhat 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.00047 | $0.00232 |
| Opus 5 | $0.00023 | $0.00116 |
| Sonnet 5 | $0.00009 | $0.00046 |
| Haiku 4.5 | $0.00005 | $0.00023 |
Grade A, and why
copyright-headers 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 3d 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
copyright-headers skill
All Rust (.rs) files in Wassette must begin with the Microsoft copyright
header, placed at the very top of the file and followed by a blank line before
any other content (including crate-level documentation and imports).
Required format
// Copyright (c) Microsoft Corporation.
// Licensed under the MIT license.
Apply headers
Run the idempotent helper, which adds the header to any file missing it and leaves existing headers untouched, so it is safe to run repeatedly:
./scripts/copyright.sh
Verify
grep -q "Copyright (c) Microsoft Corporation" your_file.rs
Apply the header before committing new files; the format must match exactly as shown above.
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.
- 3d ago First seen · 37 lines · 47 tokens per session scan A c107d3bc595c
copyright-headers is a skill published in the GitHub repository microsoft/wassette (938 stars, last pushed 4d ago), licensed MIT. It adds 47 tokens to every session and 232 once invoked, about $0.0002 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
update-keyboard-shortcuts
Audits and synchronizes keyboard shortcuts across docs/keyboardshortcuts.md, crates/regenerator2000-tui/src/ui/dialogkeyboardshortcut.rs, crates/regenerator2000-tui/src/ui/menu.rs, and the view files (viewdisassembly.rs, viewhexdump.rs, viewcharset.rs, viewbitmap.rs, viewblocks.rs, viewsprites.rs).
coding
Skill "coding" from ricardoquesada/regenerator2000, covering 6502 disassembler expert skills, core context, technical requirements, 1. 6502 logic and 2. rust performance & safety.
rust-best-practices
Rust coding best practices for cc-audit development. Use when writing new Rust code, reviewing code, or refactoring. Covers error handling, safety, performance, and idiomatic patterns.
rust-modern-style
Apply rag-rat's Rust style when writing or reviewing Rust: current stable idioms, module-qualified free functions and constants, explicit persistence contracts, and narrow APIs.
add-module
Add a new crate to the bioprism workspace implementing a blueprint section, including registering it, choosing dependencies without creating cycles, and the honesty conventions every crate must follow. Use when starting a new module, when asked to cover an uncovered blueprint section, or when setting up work for a…
verify-crate
Verify a bioprism crate is genuinely green — tests passing and clippy at zero warnings — and recognise the environment failures that masquerade as test failures. Use before claiming a crate is done, after landing an agent's work, when a test count looks wrong or lower than expected, or when cargo test reports a…