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 how-to-flowgit 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/how-to-flow)<a href="https://agentmods.dev/skills/quantumbfs/sci-brain/how-to-flow"><img src="https://agentmods.dev/badge/skills/quantumbfs/sci-brain/how-to-flow/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/how-to-flow"><img src="https://agentmods.dev/badge/skills/quantumbfs/sci-brain/how-to-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Excessive Agency · line 186 Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.Fix: Set explicit rate limits, timeouts, and resource quotas for API calls, file operations, and compute. Implement circuit breakers for runaway loops.
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.00035 | $0.02890 |
| Opus 5.5 | $0.00014 | $0.01156 |
| Sonnet 5.5 | $0.00007 | $0.00578 |
| Haiku 4.5 | $0.00003 | $0.00289 |
Grade A, and why
how-to-flow 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 — 216 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/.
Flow
A deep-thinker that conquers one hard problem by autonomous search, modeled on a CDCL/DPLL SAT solver. Given a goal, it iterates — assume, follow consequences, hit walls, learn from the walls, jump back, and re-aim when truly stuck — until a solution emerges or it converges on an equally-valuable reachable goal.
Scope. Goal-locked, fully autonomous, domain-agnostic. This is not brainstorm-ideas
(open-ended, collaborative, research-only). Use how-to-flow when you already have a specific hard target
and want a relentless solver thrown at it. KB-optional: if <project>/.knowledge/INDEX.md exists,
treat its papers as a fact source for propagation; never require it.
The mental model
| Solver concept | Here |
|---|---|
| Variable assignment (Decide) | what-if: assume a new condition |
| Unit propagation (BCP) | simulate: run consequences forward, reflect |
| Conflict | a contradiction or dead-end on the current branch |
| Conflict analysis + learned clause | the note taken after every trial |
| Non-chronological backtracking | backjump to the real cause, not one step |
| Restart (clauses kept) | pivot: re-aim the goal; notes survive |
| Decision heuristic (VSIDS) | pick the lever that shrinks distance most + is easiest; favor conditions seen in recent conflicts |
What ships with it
1 file 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.
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 · +12 lines 915980192db6
- 1mo ago First seen · 204 lines · 35 tokens per session scan A 9de5dc127652
how-to-flow is a skill published in the GitHub repository QuantumBFS/sci-brain (101 stars, last pushed 23d ago), licensed MIT. It adds 35 tokens to every session and 2,890 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…