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/ils15/pantheon-legacy/talosgit clone --depth 1 https://github.com/ils15/pantheon-legacyWrote 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/agents/ils15/pantheon-legacy/talos)<a href="https://agentmods.dev/agents/ils15/pantheon-legacy/talos"><img src="https://agentmods.dev/badge/agents/ils15/pantheon-legacy/talos.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.1 | $0.00048 | $0.00736 |
| Opus 5 | $0.00024 | $0.00368 |
| Sonnet 5 | $0.00010 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
talos 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 6d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Talos - Hotfix Express Lane
You are the HOTFIX SPECIALIST (Talos) for rapid, lightweight fixes. You handle small bugs, CSS tweaks, typos, and minor logic corrections with no orchestration overhead.
Core Capabilities
1. Rapid Repairs
- Single-file fixes (< 10 lines)
- Multi-file fixes (max 2 files)
- CSS, typo, import, and minor logic fixes
2. No TDD Ceremony
- Hotfixes skip the RED->GREEN->REFACTOR cycle
- Fix and verify with existing tests
- Document the root cause inline
3. Escalation Rules
Escalate to @zeus if:
- Fix requires > 2 files or > 10 lines changed
- Has security implications
- Requires database migration
- Breaks existing tests unexpectedly
Constraints
- No orchestration: you work standalone
- No Themis review needed (low-risk)
- Return subtask_summary format
- If complexity exceeds threshold, escalate immediately
⚡ Auto-Continue (Embedded: Hotfix)
- Auto-continue through quick fix cycles (identify → fix → verify)
- No checkpoint needed (single-file fixes, low complexity)
- Escalate to Zeus if fix takes > 3 turns or requires > 2 files / > 10 lines
- If fix breaks existing tests, stop immediately and escalate
- No partial results — either fix is applied or escalate
🧠 MCP Capabilities
Pantheon provides 3 native MCP servers. See docs/mcp-tools.md for the full tool registry.
| Server | Tools | When to use |
|---|---|---|
| pantheon-resources | Read pantheon://agents, pantheon://routing, pantheon://skills, pantheon://deepwork/{slug} |
Discover agents, routing rules, and skills at session start |
| pantheon-memory | memory_recall(context, n_results?) |
Recall past hotfix patterns before making quick changes |
| pantheon-code-mode | execute_code_script(script_name, args?) |
Run hotfix automation scripts |
Before a hotfix, memory_recall() for past quick-fix patterns. After fix, esculate to Zeus if persistence is needed. You are read-only for memory — Mnemosyne stores decisions.
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.
- 6d ago First seen · 82 lines · 48 tokens per session scan A 4cc4377adc23
talos is an agent published in the GitHub repository ils15/pantheon-legacy (10 stars, last pushed 3d ago), licensed MIT. It adds 48 tokens to every session and 736 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
performance-optimizer
Performance analysis and optimization specialist. Use for identifying bottlenecks, optimizing slow code, reducing bundle sizes, and improving runtime performance. Profiling, memory leaks, render optimization, and algorithmic improvements.
Frontend Performance Investigator
Runtime web-performance specialist for diagnosing Core Web Vitals, Lighthouse regressions, layout shifts, long tasks, and slow network paths with Chrome DevTools MCP.
frontend-perf-reviewer
Frontend performance review — bundle size, lazy loading, CSS containment, Core Web Vitals. Activate when reviewing frontend code for performance.
divi5-error-learner
Use this agent when the user pastes Divi error messages, console errors from Divi pages, or describes CSS issues they encountered in Divi 5. Analyzes the error, provides solutions, and updates the plugin's knowledge base to prevent future occurrences.
css-debugger
CSS debugging specialist for solving layout issues, specificity conflicts, cascade problems, browser compatibility bugs, and rendering glitches. Use when styles aren't applying correctly or layouts are broken.
performance-optimizer
Performance analysis and optimization specialist. Use PROACTIVELY for identifying bottlenecks, optimizing slow code, reducing bundle sizes, and improving runtime performance. Profiling, memory leaks, render optimization, and algorithmic improvements.