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.
git clone --depth 1 https://github.com/gustavobarbosab/sageWrote 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/commands/gustavobarbosab/sage/sage-behavior)<a href="https://agentmods.dev/commands/gustavobarbosab/sage/sage-behavior"><img src="https://agentmods.dev/badge/commands/gustavobarbosab/sage/sage-behavior/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/gustavobarbosab/sage/sage-behavior"><img src="https://agentmods.dev/badge/commands/gustavobarbosab/sage/sage-behavior.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00534 |
| Opus 5.5 | $0.00000 | $0.00214 |
| Sonnet 5.5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
sage-behavior 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 2mo 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sage-behavior
Use this prompt to generate behavior.md from spec.md — with the ambiguity gate that surfaces open questions BEFORE writing test cases.
This is the most important step in SAGE. The open questions section catches gaps that would otherwise become bugs or PR comments later.
Prompt
You are SAGE, a spec-first AI development assistant.
Read spec.md and the harness file (.sage/harness.md or in project knowledge).
Generate a behavior.md document with EXACTLY this structure:
## Open Questions
List every ambiguity, missing detail, or behavioral decision you found while
analyzing the spec. Format each one as:
- [ ] <question>
Be thorough. Surface anything where:
- The spec is silent on expected behavior
- Two interpretations are equally valid
- An edge case isn't explicitly covered
- A constraint conflicts with another
If you genuinely found no ambiguities, write: "- No open questions."
Do NOT skip this section.
## Test Cases
> ⚠️ Pending resolution of open questions above. Do not finalize.
After I resolve the open questions (by marking each [ ] as [x] or by updating
spec.md), regenerate this section using BDD Given/When/Then format.
Group scenarios under:
- Happy path
- Validation
- Edge cases
- Error handling
For each scenario, provide TWO versions:
**Scenario: <Short title>**
Short → <one-line condensed form>
Full:
- Given <precondition>
- When <action>
- Then <expected outcome>
- And <additional assertion if needed>
---
DO NOT generate code. Only the behavior document.
DO NOT skip the Open Questions section.
DO NOT finalize Test Cases until I confirm the open questions are resolved.
Workflow
- Run this prompt
- The AI returns
behavior.mdwith open questions and a placeholder test section - Resolve each open question — either:
- Answer it inline in the chat, OR
- Mark
[ ]as[x]inbehavior.mdwith the answer, OR - Update
spec.mdto remove the ambiguity entirely
- Tell the AI to finalize the test cases
- The final
behavior.mdis committed before any code generation
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.
- 2mo ago First seen · 84 lines · 0 tokens per session scan A 1022aa177872
sage-behavior is a command published in the GitHub repository gustavobarbosab/sage (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 534 tokens. 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 commands, from other repositories
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.
speckit.tdd.plan
Derive the feature's test list by delegating to zfa tdd plan (deterministic engine); falls back to LLM-guided derivation only when zfa is unavailable.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
dashboard
Generar dashboard HTML local con métricas de eficiencia del proyecto SDD.