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 skills add gustavobarbosab/sage --skill claudegit 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/skills/gustavobarbosab/sage/claude)<a href="https://agentmods.dev/skills/gustavobarbosab/sage/claude"><img src="https://agentmods.dev/badge/skills/gustavobarbosab/sage/claude.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.00122 | $0.01111 |
| Opus 5 | $0.00061 | $0.00556 |
| Sonnet 5 | $0.00024 | $0.00222 |
| Haiku 4.5 | $0.00012 | $0.00111 |
Grade A, and why
sage 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 8d 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.
This is a copy
100% identical to sage — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAGE
Spec · Assert · Generate · Export
A spec-first workflow that combines SDD, BDD, and Harness Engineering to front-load thinking and back-load generation.
spec.md → behavior.md → code → pr.md + doc.md
(you) (you + AI) (you + AI) (AI + you)
Commands
The user interacts with SAGE using /sage <command> [argument].
| Command | Argument | Reference file | Output |
|---|---|---|---|
/sage spec <description> |
Feature description, ticket text, or idea | references/spec.md |
Interview → spec.md + behavior.md |
/sage behavior |
(none — reads spec.md) | references/behavior.md |
behavior.md (standalone regeneration) |
/sage code |
(none — reads spec.md + behavior.md) | references/code.md |
Implementation files |
/sage update <feedback> |
Precise feedback tied to spec or behavior | references/update.md |
Updated files |
/sage pr |
(none — reads full context) | references/pr.md |
pr.md |
/sage doc |
(none — reads full context) | references/doc.md |
doc.md |
/sage harness init |
(none — interactive wizard) | references/harness-init.md |
.sage/harness.md |
/sage harness generate |
(none — reads codebase files) | references/harness-generate.md |
.sage/harness.md |
/sage harness review |
(none — reads harness.md) | references/harness-review.md |
Review report |
How to handle each command
When the user types a /sage command:
- Identify the sub-command from the table above
- Read the corresponding reference file — it contains the full prompt and instructions for that step
- Extract the inline argument if provided (e.g.
/sage spec "Login screen with email and password"→ argument is"Login screen with email and password") - Execute the step following the reference file instructions
If the user types /sage with no sub-command, show the command table above and ask which step they want to run.
Special flow for /sage spec
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- README.md 1.1 KB
- references/behavior.md 2.6 KB
- references/code.md 1.6 KB
- references/doc.md 1.4 KB
- references/harness-generate.md 1.6 KB
- references/harness-init.md 1.9 KB
- references/harness-review.md 1.4 KB
- references/pr.md 1.4 KB
- references/spec.md 4.6 KB
- references/update.md 1.7 KB
- sage.skill 13 KB
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.
- 8d ago First seen · 93 lines · 122 tokens per session scan A c31ab0352a62
sage is a skill published in the GitHub repository gustavobarbosab/sage (2 stars, last pushed 2mo ago), licensed MIT. It adds 122 tokens to every session and 1,111 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to sage, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…