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/ftshare-lab/agent-claim-network/verifynpx skills add FTShare-Lab/agent-claim-network --skill verifygit clone --depth 1 https://github.com/FTShare-Lab/agent-claim-networkWrote 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/ftshare-lab/agent-claim-network/verify)<a href="https://agentmods.dev/skills/ftshare-lab/agent-claim-network/verify"><img src="https://agentmods.dev/badge/skills/ftshare-lab/agent-claim-network/verify.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 | $0.00036 | $0.00243 |
| Opus 5 | $0.00018 | $0.00121 |
| Sonnet 5 | $0.00007 | $0.00049 |
| Haiku 4.5 | $0.00004 | $0.00024 |
Grade A, and why
verify 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 4d 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
Verify ACN
Run from the repository root. Load the local environment file when present, but never print its contents:
if [[ -f export_env.sh ]]; then
source export_env.sh
fi
scripts/check_version_consistency.sh
cargo fmt --check
cargo clippy -- -D warnings
cargo test
cargo check
Report each command's result. Stop and diagnose failures instead of skipping the remaining verification silently.
When the change affects src/session_tui/, interactive behavior in src/bin/acn.rs, terminal rendering, input handling, or TUI-facing help/status text, also follow ../tui-smoke-test-with-tmux/SKILL.md and run:
.agents/skills/tui-smoke-test-with-tmux/scripts/tui_tmux_smoke.sh
Treat the bundled script's current assertions and captured stderr.log as authoritative; do not duplicate old prompt or footer strings in this skill.
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.
- 4d ago First seen · 30 lines · 36 tokens per session scan A eb3245c6f649
verify is a skill published in the GitHub repository FTShare-Lab/agent-claim-network (41 stars, last pushed 4d ago), licensed Apache-2.0. It adds 36 tokens to every session and 243 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
cargo-test
Skill "cargo-test" from rootwarp/claude-code-plugins-monorepo, covering /cargo-test and instructions.
js-in-html-testing
Test JS logic embedded in HTML using two-layer strategy - Python unit tests + Playwright browser integration tests.
rust-unit-tests
Write, improve, and run Rust unit tests in the warp Rust codebase.
check
Run Rust fmt, clippy, and unit tests. Use after making Rust code changes.
check-model
Check model compatibility with xinfer before loading. Validates config.json, weight tensor shapes and naming, quantization format correctness, and multi-rank (tensor-parallel) divisibility. Use when the user asks to check, validate, audit, or verify a model will load correctly — from a HuggingFace URL/config, local…
test-model
Test LLM models served by xinfer for correctness, output quality, and performance. Use when the user asks to test, benchmark, validate, or verify models — either from a local folder path or HuggingFace model IDs. Supports all xinfer-compatible formats: BF16, FP8, MXFP4, NVFP4, GGUF, GPTQ, AWQ, ISQ, Dense, MoE, and…