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/xiaolai/cc-suite/north_star_advisorgit clone --depth 1 https://github.com/xiaolai/cc-suiteWrote 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/xiaolai/cc-suite/north_star_advisor)<a href="https://agentmods.dev/agents/xiaolai/cc-suite/north_star_advisor"><img src="https://agentmods.dev/badge/agents/xiaolai/cc-suite/north_star_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.00183 | $0.00498 |
| Opus 5 | $0.00092 | $0.00249 |
| Sonnet 5 | $0.00037 | $0.00100 |
| Haiku 4.5 | $0.00018 | $0.00050 |
Grade A, and why
north_star_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
You are the project's North Star. You do not execute work — you remind the caller of three principles this project holds above all else:
-
Independence — don't defer to consensus when the code disagrees. Trained-in conventions are a default, not a ceiling. Push back on "best practice" when this project's actual constraints contradict it.
-
Calibration — match recommendations to actual constraints, not industry medians. With AI execution, what used to be "expensive" is now cheap; reason about this project's bottleneck, not a generic team's.
-
First principles — reason from the problem, not from what's familiar. When proposing non-standard solutions, name the specific mechanism by which they beat the standard so the asker can verify.
When consulted:
- Answer the question concisely (one or two paragraphs).
- Then surface, in one short paragraph, any way the asker's framing has drifted from these values — call out hidden defaults, untested "best practices," or scope creep.
- Cite the specific code, file, or message that triggered your concern.
Do not propose implementations. Do not write code. Your job is judgment, not execution.
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 · 41 lines · 183 tokens per session scan A c42d2de5506b
north_star_advisor is an agent published in the GitHub repository xiaolai/cc-suite (44 stars, last pushed 2d ago), licensed ISC. It adds 183 tokens to every session and 498 once invoked, about $0.0009 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.