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/qgolem/orc/archnpx skills add qGolem/orc --skill archgit clone --depth 1 https://github.com/qGolem/orcWhat 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.00024 | $0.04599 |
| Opus 5 | $0.00012 | $0.02299 |
| Sonnet 5 | $0.00005 | $0.00920 |
| Haiku 4.5 | $0.00002 | $0.00460 |
Grade B, and why
arch scanned grade B with 1 finding 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 2d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- [ ] Compiles without warnings How it starts
The opening of the file, as written. The whole thing — 569 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arch — Rust Project Orchestrator
Multi-phase Rust project architect. Gathers requirements interactively, designs architecture using rust-architect patterns, implements with rust-expert knowledge, then spawns a parallel review wave with rust-skills + cargo-fuzz. No frontend — pure Rust.
Skill dependencies: This skill expects rust-architect, rust-skills, cargo-fuzz, property-based-testing, and zeroize-audit installed at .claude/skills/, and rust-expert at .claude/agents/. Install via /orc:install. If installed globally at ~/.claude/ instead, adjust paths accordingly.
CRITICAL RULES
- Execute steps in order. Do NOT skip, reorder, or merge steps.
- Write output files. Each step produces its file in
.arch/before the next begins. - Stop at checkpoints. PHASE CHECKPOINTs require explicit user approval via AskUserQuestion.
- Halt on failure. If any step fails, STOP and present the error.
- Never enter plan mode. This skill IS the plan — execute it.
- No frontend. Skip any UI/browser/component work. Pure Rust.
- Team only for Step 5. TeamCreate/TeamDelete scoped to the review wave only.
Pre-flight
Check for existing session
If .arch/state.json exists with status: "in_progress":
Found an in-progress arch session:
Feature: [name]
Current step: [step]
Ask via AskUserQuestion:
- Resume — continue from saved step
- Start fresh — archive to
.arch-archived-{date}/, create new.arch/
Initialize
mkdir -p .arch
Write .arch/state.json:
{
"feature": "$ARGUMENTS",
"status": "in_progress",
"crate_type": "auto-detect",
"async_runtime": "auto-detect",
"current_step": 1,
"current_phase": 1,
"completed_steps": [],
"files_created": []
}
Detect from project:
Cargo.toml→ crate type (bin/lib/workspace from[package]or[workspace])tokioin deps → async runtime- Parse
--crateand--asyncflags from$ARGUMENTSas overrides
Phase 1: Design (Steps 1-2) — Interactive
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.
- 2d ago First seen · 569 lines · 24 tokens per session scan B c9bd48e9b1ee
arch is a skill published in the GitHub repository qGolem/orc (5 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 4,599 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
rust-skills
Comprehensive Rust coding guidelines with 265 rules across 26 categories. Use when writing, reviewing, or refactoring Rust code. Covers ownership, error handling, async patterns, concurrency, unsafe code, API design, memory optimization, performance, numeric safety, conversions, serde, pattern matching, macros…
rust-patterns
Rust patterns covering ownership, lifetimes, error handling, traits, async with Tokio, and smart pointers. Activate when writing or reviewing Rust.
cli-forge-data
Design and implement safe PostgreSQL database changes for Rust/SQLx applications. Use for new schemas, migrations, constraints, indexes, repositories, transaction boundaries, state machines, idempotency, concurrency control, queues, multi-tenancy, soft deletion, ledgers, outbox/inbox, repair jobs, or corrections…
anti-ai-slop
Apply this skill when auditing, writing, or reviewing Rust code to avoid generic "AI slop" patterns: boilerplate structs with no purpose, copy-paste error handling, meaningless variable names, over-engineered abstractions, or hollow documentation. Triggers: "this looks AI-generated", "too much boilerplate"…
rust-review
Rust Code Review: Reviews Rust code for ownership patterns, lifetime management, unsafe usage, error handling with Result/Option, concurrency safety, and idiomatic Rust patterns. Covers async Rust (tokio/async-std), trait design, macro hygiene, and performance. Use when the user wants a review of Rust code, mentions…
next-rspack
Maintain @next/rspack-core and @next/rspack-binding packages. Use when editing rspack/package.json, rspack/crates/binding/Cargo.toml, rspack/rust-toolchain.toml, or packages/next-rspack/package.json. Covers upgrading @rspack/core npm version, rspack crate versions, Rust toolchain version, building and linking for…