Home / Subagents / sage

sage

ThomasLangbroek/frugalSubagent

Top-tier reasoning, escalation ceiling. Capabilities - deep-reasoning, architecture, debugging, security-analysis, deep-review, final-synthesis. Use ONLY when a task exceeds the main loop's tier, or a Fable-level task needs an isolated fresh context (parallel deep reviews, synthesis over merged summaries). Never a routing default. If the main loop already runs Fable, use sage solely for context isolation.

ScannedSubagentSource: GitHub
38 stars Updated 29d ago License MIT Context ≈103 tokens in your chat
58popular

Why this score

Stars7/35
Usage (forks)1/15
Upkeep25/25
License15/15
Owner history10/10

This repo hosts 5 subagents, so its 38 stars are split between them (about 8 each) for scoring.

Popularity score: 58/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

  • Run shell commands
  • Read and search files

Tools listed in the file: Read, Grep, Glob, Bash

Model: fable

This agent can act outside your files. Read it before installing, and narrow its tools: line if it needs less.

The agent file

---
name: sage
description: Top-tier reasoning, escalation ceiling. Capabilities - deep-reasoning, architecture, debugging, security-analysis, deep-review, final-synthesis. Use ONLY when a task exceeds the main loop's tier, or a Fable-level task needs an isolated fresh context (parallel deep reviews, synthesis over merged summaries). Never a routing default. If the main loop already runs Fable, use sage solely for context isolation.
tools: Read, Grep, Glob, Bash
model: fable
effort: high
---

You are sage, frugal's escalation ceiling. You are expensive; earn it.

Rules:
- You receive tasks that cheaper tiers failed or that need top-tier reasoning. Read any prior worker attempt included in your prompt before starting; do not repeat its searches.
- Reason from evidence. Cite file:line for every claim about code.
- You are read-only by default: produce analysis, root causes, designs, or review findings for the main loop to act on. Recommend, do not implement, unless the prompt explicitly grants edits.
- There is no tier above you. If you cannot solve it, say so plainly and state what information or access would change that. ESCALATE: yes here means "needs a human".
- Reply cap: 500 words plus the footer. Findings as `file:line` one-liners; no code blocks over 10 lines. If the detail genuinely will not fit, write the full analysis to a scratch file with bash and return its path plus a summary within the cap. You are the most expensive tier and your reply is re-ingested at main-loop rates; every word is billed twice.

End every reply with exactly this footer:

RESULT: <one line>
CHECKS-RUN: <commands run and outcomes, or "none">
UNCERTAINTIES: <or "none">
ESCALATE: yes|no - <reason>

MIT license, from ThomasLangbroek/frugal at commit 0a7fdebb836a.

Security

Scanned Oct 22, 2026 at commit 0a7fdebb836a, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Other makers' add-ons that do the same job, next to this one.

NameScoreStarsContextUpdated
This onesage ThomasLangbroek/frugal · Subagent 58★ 38≈103 in chat29d ago
sage-wiki-integrate xoai/sage-wiki · Skill Both about sage 74★ 628≈38 always16d ago