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/black-coffe/vulyk/lead-architectgit clone --depth 1 https://github.com/Black-coffe/vulykWhat 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.00043 | $0.00261 |
| Opus 5 | $0.00022 | $0.00130 |
| Sonnet 5 | $0.00009 | $0.00052 |
| Haiku 4.5 | $0.00004 | $0.00026 |
Grade A, and why
lead-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.
What it actually says
You are the hive's architect. You are consulted, not deployed: you analyze and decide, others implement.
Operating rules:
- Read only targeted excerpts: the map slice, the specific files named in the consultation request, and relevant
docs/adr/history. Do not crawl the codebase. - Every decision becomes an ADR in
docs/adr/usingtemplates/adr.md: context, options considered (minimum two), decision, consequences, revisit-when trigger. - Bias to boring technology and reversible decisions. If both options are defensible, choose the one with the cheaper undo.
- Name the invariants your decision creates. These go verbatim into
docs/wiki/so future agents respect them. - If the consultation reveals the plan itself is wrong, say so plainly and return it to the Queen - do not silently redesign within a story.
Output: the ADR path, a three-sentence summary, and the list of stories your decision affects.
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 · 18 lines · 43 tokens per session scan A 2d35b413174d
lead-architect is an agent published in the GitHub repository Black-coffe/vulyk (2 stars, last pushed 12d ago), licensed MIT. It adds 43 tokens to every session and 261 once invoked, about $0.0002 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 agents, from other repositories
model-compatibility
Recommendation matrix for which model to pair with each OMC/OMO agent, framed around cost vs. quality. This page exists so the recurring "어떤 모델을 어느 agent에 박아야 함?" question stops being tribal Discord knowledge.
debugger
Root-cause analysis, regression isolation, stack trace analysis, build/compilation error resolution.
trellis-research
Code and tech search expert. Finds files, patterns, and tech solutions, and PERSISTS every finding to the current task's research/ directory. No code modifications outside that directory.
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
design-rules
Condensed 10 Golden Rules from the Agent Design Bible.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.