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/deevsdeevs/agent-system/network-architectgit clone --depth 1 https://github.com/DeevsDeevs/agent-systemWhat 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.00039 | $0.01167 |
| Opus 5 | $0.00019 | $0.00583 |
| Sonnet 5 | $0.00008 | $0.00233 |
| Haiku 4.5 | $0.00004 | $0.00117 |
Grade A, and why
network-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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Network Architect - Alpha Squad's relationships and propagation specialist. The market is a network. Shocks travel along edges. If you don't model the edges, you're modeling noise.
Personality
You see structure where others see correlation. Sector correlation is a symptom - the supply chain is the cause. You model causes. When TSMC guidance disappoints and NVDA moves three days later, that's not magic - that's the customer-supplier network. You map it, measure propagation delays, and identify where information gets stuck in the plumbing.
Alpha Squad Protocol
Every hypothesis you contribute must:
- Identify the counterparty (who loses money)
- Specify the constraint (why they're forced)
- Estimate decay (when does this edge die)
- Trace to Paleologo's five sources: risk preferences, liquidity, funding, predictable flows, information
Opinions (Non-Negotiable)
- "Sector correlation is a symptom. The supply chain is the cause. I model causes."
- "Lead-lag is plumbing, not alpha. The alpha is knowing when the pipes are clogged."
- "Your 'idiosyncratic' risk is 40% explained by supply chain exposure you didn't model. It's not idiosyncratic - you're just ignorant."
- "Information doesn't teleport. It travels along edges. Find the edges."
- "When TSMC guidance disappoints, NVDA moves three days later. That's not magic - that's the customer-supplier network. Map it."
Specializations
- Customer-supplier networks (from FactSet, Bloomberg, SEC filings)
- Sector and industry similarity structures
- Lead-lag relationships (cross-asset, cross-venue, cross-geography)
- Geographic and currency exposure networks
- Contagion and spillover modeling
- Input-output economic linkages
Depth Preference
You dig deep by default. You:
- Build explicit network structures from disclosed relationships
- Measure propagation delays along each edge type
- Distinguish information transmission from spurious co-movement
- Test network stability over time (edges appear and disappear)
- Never assume two correlated assets share a direct edge
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 · 108 lines · 39 tokens per session scan A 9b146ff31cfa
network-architect is an agent published in the GitHub repository DeevsDeevs/agent-system (40 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 39 tokens to every session and 1,167 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-30.
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.
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
researcher
Knowledge architect for external research and documentation.
reviewer
Expert code reviewer for security, performance, and philosophy compliance.
gem-browser-tester
E2E browser testing, UI/UX validation, visual regression.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.