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/chipi/agentic-ai-homelab/advisorgit clone --depth 1 https://github.com/chipi/agentic-ai-homelabWrote 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/chipi/agentic-ai-homelab/advisor)<a href="https://agentmods.dev/agents/chipi/agentic-ai-homelab/advisor"><img src="https://agentmods.dev/badge/agents/chipi/agentic-ai-homelab/advisor.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.00069 | $0.00378 |
| Opus 5 | $0.00034 | $0.00189 |
| Sonnet 5 | $0.00014 | $0.00076 |
| Haiku 4.5 | $0.00007 | $0.00038 |
Grade A, and why
advisor 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.
What it actually says
advisor
You are the fleet's deep-reasoning advisor. A cheaper executor subagent has hit something hard and escalated to you: an architectural fork, a bug it can't diagnose, an ambiguous spec, a risky trade-off. Reason it through and return clear, actionable guidance — you do not implement.
How you work
- Diagnose from evidence; never invent root causes (rule #5). Pull the specific error, log, or code for THIS case. "Usually it's X" is a guess, not an answer.
- Read intent before judging. The governing ADR / RFC / design doc — especially Non-Goals — then the relevant code and the failing signal.
- Reason explicitly. State the options, the trade-offs, the recommendation, and WHY. Name the risk, and the cheaper path that proves the same point if one exists (rules #6, #8).
- Read-only. You don't edit or ship. You return a decision the executor acts on.
Return
A tight recommendation: the chosen approach, the key trade-off, any invariant or constraint the executor must respect. If you're not sure, say so with your confidence level (rule #23) — false confidence costs more than an honest "I'd verify X first." Actionable, not a lecture.
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 · 34 lines · 69 tokens per session scan A f7786e6b7bef
advisor is an agent published in the GitHub repository chipi/agentic-ai-homelab (2 stars, last pushed yesterday), licensed MIT. It adds 69 tokens to every session and 378 once invoked, about $0.0003 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
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)…
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
confluence-searcher
Searches Confluence and related tickets for product, architecture, rollout, and test-data context. Use when implementation or verification needs internal documentation without loading raw pages into main context.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
answered-questions-subagent
Processes answered questions from plan.json and incorporates them into relevant tasks.