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 agents/viksant/vibe-coding-tools-content/cloud-architectgit clone --depth 1 https://github.com/viksant/vibe-coding-tools-contentWhat 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.00071 | $0.01935 |
| Opus 5 | $0.00036 | $0.00967 |
| Sonnet 5 | $0.00014 | $0.00387 |
| Haiku 4.5 | $0.00007 | $0.00194 |
Grade A, and why
cloud-architect 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 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.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 167 lines · 71 tokens per session scan A f080d31f2906
cloud-architect is an agent published in the GitHub repository viksant/vibe-coding-tools-content (44 stars, last pushed 2mo ago), with no licence file. It adds 71 tokens to every session and 1,935 once invoked, about $0.0004 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 agents, from other repositories
writing-skills
The skills under skills/ are staged into a sandbox and run autonomously against a target repo — no human is in the loop mid-run. A skill exists to wrangle determinism out of a stochastic agent: the goal is predictability, the agent taking the same process every run (not producing the same output). Everything below…
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
software-engineer
Use this agent to implement source code and tests from an approved IPLAN. Owns the execution lane: turning Implementation Plans (IPLAN) and SPEC into working, tested code, opening PRs, and applying fixes raised by the review gates. Only operates on approved (ai:ready) scope.
ss-reviewer
Independent code reviewer for the specship review stage — one member of the opt-in review panel. Use to get fresh, context-free eyes on a working diff, optionally through a named lens (correctness, security, performance, contract-consistency). Reports findings only; it does not fix code, decide the verdict, or touch…
ss-researcher
External-fact search worker for the specship research stage. Use to run one query angle of a larger question and return verified, cited conclusions. One invocation per angle — it gathers and checks its own sources, and it neither picks the angles nor writes the report.
ss-explorer
Read-only search worker for the specship pipeline. Use to delegate one wide fan-out sweep when a stage needs an answer that means reading many files — it returns verified conclusions only, so the caller's context stays clean. A stage invokes it, never a user directly; it never writes or changes code.