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/coleam00/archon/test-releasenpx skills add coleam00/Archon --skill test-releasegit clone --depth 1 https://github.com/coleam00/ArchonWrote 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/coleam00/archon/test-release)<a href="https://agentmods.dev/skills/coleam00/archon/test-release"><img src="https://agentmods.dev/badge/skills/coleam00/archon/test-release.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.00145 | $0.05924 |
| Opus 5 | $0.00072 | $0.02962 |
| Sonnet 5 | $0.00029 | $0.01185 |
| Haiku 4.5 | $0.00015 | $0.00592 |
Grade F, and why
test-release scanned grade F with 4 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 today.
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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
> checksum, then demands sudo and dies with Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
> assignment applies only to `cmd1`, so `INSTALL_DIR=… curl … | bash` sets it for Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "$LEAKREPO" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Triggers: "test the release", "test 0.3.1 via brew", "verify the curl install", How it starts
The opening of the file, as written. The whole thing — 543 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Release
Automated smoke test for a released archon binary. Covers three install paths:
brew— Homebrew tap on macOS (tests the formula and checksums)curl-mac—curl install.shon macOS (tests the install script, sandboxed to a temp dir)curl-vps—curl install.shon a remote Linux VPS (tests the Linux binary and full install path)
Every path installs the binary, runs a fixed smoke test suite, and cleans up. The dev bun link binary is never touched and remains the default archon on PATH throughout.
When NOT to use this skill:
- There is no release yet — build a local binary via
bash scripts/build-binaries.shand run it fromdist/binaries/directly - You want to test the dev clone — use
bun run validateor invoke source directly viabun packages/cli/src/cli.ts - You want to test the full server + web UI deploy flow — use the cloud-init from
deploy/cloud-init.ymlon a real VPS
Local build for pre-release QA
To build a binary locally with the exact same flags and constants that CI uses,
invoke scripts/build-binaries.sh directly. The script supports two modes:
# Multi-target mode (builds all 4 local platforms into dist/binaries/)
VERSION=0.3.1 GIT_COMMIT=abc12345 bash scripts/build-binaries.sh
# Single-target mode (matches one CI matrix job)
VERSION=0.3.1 \
GIT_COMMIT=abc12345 \
TARGET=bun-darwin-arm64 \
OUTFILE=dist/test-archon-darwin-arm64 \
bash scripts/build-binaries.sh
# Verify the binary — use the path from the mode you built:
# multi-target → ./dist/binaries/archon-darwin-arm64
# single-target → the OUTFILE you passed above
./dist/test-archon-darwin-arm64 version
# Expected: Archon CLI v0.3.1, Build: binary, Git commit: abc12345
Run this before tagging a release to catch build-time-constant issues locally. The script is the canonical entry point — both local dev and the release workflow call it the same way, so a green local build means the CI build will exercise the same code path.
Phase 1 — Determine scope
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.
- today First seen · 543 lines · 145 tokens per session scan F 89c306fbc0e2
test-release is a skill published in the GitHub repository coleam00/Archon (23,366 stars, last pushed yesterday), licensed MIT. It adds 145 tokens to every session and 5,924 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it F with 4 findings (asks for root, downloads and executes remote code, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
system-prompts
Write system prompts, tool docs, and agent definitions. Project tag conventions + RFC 2119 keywords + dense compression. Use when authoring or editing any prompt the model reads.
tool-prompt-optimization
Optimize the description prompts an AI agent reads to learn its built-in tools (the .md files under prompts/tools/). Two halves: (1) measure how much of a prompt is already inferable from the tool's JSON parameter schema + name, to prune redundancy with evidence; (2) house authoring rules for what belongs in a tool…
semantic-compression
Re-encode verbose prose into a dense telegraphic register — punctuation as connectives, label frames, verbless assertions — without losing normativity or precision. Use when compressing system prompts, tool/function descriptions, skill bodies, or agent instructions; reducing token count or context bloat; making…
greet
A greeting skill for testing.
mcp-setup
Configure MCP servers via a guided menu — curated bundles (Context7, Exa, Filesystem, GitHub) or a custom stdio/HTTP server — using tinycode mcp add, with scope control, verification, and troubleshooting guidance.
team
Launch a multi-agent team to work on a task in parallel.