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/lookatitude/guild/guild-operationsnpx skills add lookatitude/guild --skill guild-operationsgit clone --depth 1 https://github.com/lookatitude/guildWrote 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/lookatitude/guild/guild-operations)<a href="https://agentmods.dev/skills/lookatitude/guild/guild-operations"><img src="https://agentmods.dev/badge/skills/lookatitude/guild/guild-operations.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.00169 | $0.03861 |
| Opus 5 | $0.00084 | $0.01930 |
| Sonnet 5 | $0.00034 | $0.00772 |
| Haiku 4.5 | $0.00017 | $0.00386 |
Grade A, and why
guild-operations 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.
How it starts
The opening of the file, as written. The whole thing — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
guild:operations
Realizes DI-3 (full Operations skill) (decisions/di1-di6-contracts.md)
against the frozen guild.ops.v1 / guild.incident.v1 /
guild.release.v1 (./operations-contract.md §"guild.ops.v1 fields"). Verb
ops (never ship); gate G-operations. No cloud-build (GR-7).
The router: selects the class, enforces the cross-class rails, then
dispatches the per-class playbook guild:ops-<class>.
When to use it
At the operations phase: select a runbook class, enforce the 4 safety rails +
mandatory pre-flight, route to the matching ops-* playbook, and supply the D8
close-gate evidence join (consume-only).
When not to use it
- Quality / release-readiness →
guild:quality. - Authoring a runbook's content →
devops-*specialists. - Closing the initiative →
InitiativeCloseout(Operations only supplies evidence). - A specific class's playbook detail → the sibling
guild:ops-<class>skill.
Required inputs
- The runbook (positional
[runbook], else surfaced detection — always confirmed). - The wiki trust root
.guild/wiki/standards/runbooks/<name>.md(promoted viaguild:decisions; kept under.guild/by the P5 boundary CONTRACT — cited viaP1-ownership-001, never the guard implementation). - The additive
autonomy_contract(./operations-contract.md §Posture, pointer); frozen ops/incident/release (./operations-contract.md §"guild.ops.v1 fields"); the consumedguild.quality.v1.
What ships with it
1 file 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.
- 4d ago First seen · 240 lines · 169 tokens per session scan A 58979e029ca6
guild-operations is a skill published in the GitHub repository lookatitude/guild (7 stars, last pushed 4d ago), licensed MIT. It adds 169 tokens to every session and 3,861 once invoked, about $0.0008 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…