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 skills add Mathews-Tom/armory --skill walkthroughgit clone --depth 1 https://github.com/Mathews-Tom/armoryWrote 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/mathews-tom/armory/walkthrough)<a href="https://agentmods.dev/skills/mathews-tom/armory/walkthrough"><img src="https://agentmods.dev/badge/skills/mathews-tom/armory/walkthrough/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mathews-tom/armory/walkthrough"><img src="https://agentmods.dev/badge/skills/mathews-tom/armory/walkthrough.svg" alt="Reviewed on agentmods" width="80" 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.00051 | $0.01257 |
| Opus 5.5 | $0.00020 | $0.00503 |
| Sonnet 5.5 | $0.00010 | $0.00251 |
| Haiku 4.5 | $0.00005 | $0.00126 |
Grade A, and why
walkthrough 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Walkthrough
Turn unavoidable human work into a sourced, executable procedure. Keep agent-doable inspection, configuration and coding with the agent. A missing permission is not permission to ask the human to run a large opaque script.
1. Establish the boundary and source map
Inspect the actual repository before asking the human for facts it contains: setup documentation, example environment files, config loaders and their precedence, package scripts, deployment config and active CI workflows. Record each required setup key and each actual CI secrets.*/vars.* use with its file/line or authoritative documentation source. Dynamic names remain unresolved until their construction is traced. Do not infer that every CI key needs a local dotenv entry or vice versa.
Separate agent work from human-only work and identify the exact missing authority, physical access, private dashboard consent or knowledge for every human stage. If nothing requires a human, finish with the ordinary agent workflow instead; do not generate a ceremony. No installation, account creation, Git changes, remote writes or credential access is implied by invoking this skill.
Complete when: every requested operation is either agent-owned with a concrete action, a justified human stage, or an explicit blocked item; every captured value has an actual name, source, destination and consumer. Ask only for remaining human-held information, never for secrets in chat.
2. Agree the procedure
Show the ordered stages, their dependency order, public source pointers, secret/public classification, required/optional status and destination. For each stage distinguish: observation, reversible write, irreversible action, or human attestation. Show irreversible consequences and recovery limits before approval. Retain unknown dashboard navigation as unknown UI; use current authoritative docs or a human observation to resolve it, rather than inventing menu names. A known URL is not proof that its current UI is known.
What ships with it
8 files 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.
- 8d ago Changed 9257052d3fc7
- 9d ago First seen · 51 lines · 51 tokens per session scan A 9aa00dc8ffc7
walkthrough is a skill published in the GitHub repository Mathews-Tom/armory (337 stars, last pushed 2d ago), licensed MIT. It adds 51 tokens to every session and 1,257 once invoked, about $0.0002 per session on Opus 5.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-10-19.
Other skills, from other repositories
sandbox-to-production-gates
Defines safe sandbox-to-production promotion gates for agent-built software. Use when deploying, restarting, promoting builds, validating runtime surfaces, checking rollback readiness, or proving that the running production artefact matches the reviewed source commit.
application-integration-authoring
Builds, versions, publishes, tests, and executes Google Cloud Application Integration workflows through the REST API and Python discovery client, and promotes versions across environments. Use when listing integrations, downloading or uploading integration versions as JSON, configuring API triggers or config…
gke-alert-configuration
Configures alerting policies in Terraform for Google Kubernetes Engine (GKE) clusters, workloads, and services using PromQL and Google Cloud Managed Service for Prometheus. Use when writing, analyzing, validating, or deploying Terraform alerting policies to monitor GKE service latency, traffic, error rates using…
gke-ai-troubleshooting-tpu-partition-overlap
Diagnose and resolve GKE TPU slice creation failures (SliceCreationFailed) caused by partition overlap conflicts where requested TPU partitions or their nodes are already used by another slice or JobSet. Use when diagnosing GKE TPU slice creation failures with SliceCreationFailed partition or node conflicts. Don't use…
application-integration-basics
Explains Google Cloud Application Integration concepts, region provisioning, IAM roles, run-as service accounts, interface choices (REST, Python discovery client, Terraform, ADK), and platform limits. Use when setting up Application Integration in a Google Cloud project, enabling required APIs, provisioning a region…
cloud-run-basics
Manages Cloud Run services, jobs, and worker pools. Use when you need to deploy applications responding to HTTP requests (services), run event-triggered or scheduled tasks (jobs), or handle always-on pull-based background processing (worker pools).