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 QuantumBFS/sci-brain --skill create-advisorgit clone --depth 1 https://github.com/QuantumBFS/sci-brainWrote 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/quantumbfs/sci-brain/create-advisor)<a href="https://agentmods.dev/skills/quantumbfs/sci-brain/create-advisor"><img src="https://agentmods.dev/badge/skills/quantumbfs/sci-brain/create-advisor/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/skills/quantumbfs/sci-brain/create-advisor"><img src="https://agentmods.dev/badge/skills/quantumbfs/sci-brain/create-advisor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 36 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 64 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00023 | $0.02675 |
| Opus 5.5 | $0.00009 | $0.01070 |
| Sonnet 5.5 | $0.00005 | $0.00535 |
| Haiku 4.5 | $0.00002 | $0.00267 |
Grade A, and why
create-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 1mo 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Installed resources
Keep the working directory at the user's project. Resolve this loaded SKILL.md
with Path(path).resolve() before locating resources; follow symlinks. Bare
helpers/, references/, and template paths are relative to that real skill
directory. A path written as skills/<name>/... means the installed <name>
skill's directory from the agent's skill catalog, not a path in the user's project.
Locate each dependency by its public skill name; copied skills need not be siblings.
If a dependency is absent, report the missing skill and install it before that step.
Shared writing files are bundled in how-to-write-ideas-report/references/.
Before running the examples, set DOWNLOAD_REF_DIR to the absolute directory of how-to-download-ref. Quote these variables as shown.
Advisor Profile Generation
Onboard a contributor and create a named advisor profile. The profile captures how a real person thinks — their cognitive style, attention patterns, reasoning strengths, and conversation dynamics — so the brainstorm-ideas skill can launch them as a subagent collaborator rather than a thin inline persona.
Choose the mode
- Create an advisor: start at Step 1 and run the complete workflow.
- Update an advisor from new conversations: read the existing
advisors/<slug>/profile.md, preserve its background, then start at Step 2 with the new JSONL or Markdown sources. - Import Markdown dialogs: ask for the file paths and target advisor, then use the Markdown path in Step 2. For a new advisor, collect the Step 1 background first.
- Analyze thinking patterns only: run Conversation Pattern Extraction and stop after writing
thinking-pattern.mdandmaster-thinking.md; do not synthesize an advisor profile unless the user asks.
Step 1 — Personal Profile
Ask the contributor to provide their academic/professional background:
- (a) Tell me yourself (field, experience, what you've worked on)
- (b) Zotero library — follow the
know-me-betterskill instructions (skills/know-me-better/SKILL.md) to index publications - (c) Google Scholar profile — follow the
know-me-betterskill instructions to index publications
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.
- 1mo ago Changed · -31 lines b06f436dbade
- 1mo ago Changed · +14 lines 173ef8f64821
- 1mo ago First seen · 255 lines · 23 tokens per session scan A 12406a1d3619
create-advisor is a skill published in the GitHub repository QuantumBFS/sci-brain (101 stars, last pushed 23d ago), licensed MIT. It adds 23 tokens to every session and 2,675 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
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…
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.