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 skills/baokhang83/fluencyloop/reviewnpx skills add baokhang83/fluencyloop --skill reviewgit clone --depth 1 https://github.com/baokhang83/fluencyloopWhat 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.00077 | $0.01626 |
| Opus 5 | $0.00039 | $0.00813 |
| Sonnet 5 | $0.00015 | $0.00325 |
| Haiku 4.5 | $0.00008 | $0.00163 |
Grade A, and why
review 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 2d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fluencyloop:review — Stage 4, assemble the PR view
A feature is a branch, so the review view assembles itself: no manual linking. You turn the feature's sessions into a summary a reviewer can read to get fluent fast.
Bundled CLI (Claude Code)
Before invoking a deterministic command, use this plugin's bundled launcher:
"${CLAUDE_PLUGIN_ROOT}/bin/fluencyloop" <arguments>. Every fluencyloop … command below
means that exact Bash-tool command; it is never a chat instruction or a globally installed
command.
Do not hand-scaffold .fluencyloop/, .claude/skills/, designs, sessions, state, or helper
scripts. The bundled CLI creates the deterministic files and returns their paths.
Local site — open once
Before the first user-visible response, invoke
"${CLAUDE_PLUGIN_ROOT}/bin/fluencyloop" site --ensure --open-once --json. This ensures the
reader for every workflow entry, but opens a browser tab only once while that managed reader is
alive. If it reports running: true and no earlier assistant message in this session starts with
FluencyLoop site:, say FluencyLoop site: <url> (opened in browser). once, using its returned
URL. Do not mention an unavailable site or repeat the announcement.
Generated prose — ASD-STE100
Write generated user-facing technical prose in ASD-STE100 style: use short, direct sentences, active voice, one main action per sentence, and stable, unambiguous terms. Preserve product names, code identifiers, CLI commands, field names, and exact recorded values. Do not claim formal ASD-STE100 compliance: that requires checking the official controlled dictionary and rules.
Question delivery — preserve the pause
For a real answer, choice, or confirmation, use AskUserQuestion in Claude Code. Codex has
no equivalent question-form tool, so ask a concise standalone question in chat and stop; do not
create a PR or persist a preference until the developer answers.
1. Gather the raw material
Read .fluencyloop/state.json first if it exists — it is the loop's source of truth for the
active feature (feature slug, branch, base_ref), so you don't re-derive them from git. Use
its base_ref as the diff base (--base) rather than guessing the default branch.
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.
- 2d ago First seen · 116 lines · 77 tokens per session scan A cd3befbe6216
review is a skill published in the GitHub repository baokhang83/fluencyloop (44 stars, last pushed 17d ago), licensed Apache-2.0. It adds 77 tokens to every session and 1,626 once invoked, about $0.0004 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 skills, from other repositories
add-community-extension
Add a community extension to the Spec Kit catalog from a GitHub issue submission. USE FOR: processing extension submission issues, validating catalog entries, updating catalog.community.json and docs/community/extensions.md, creating PRs. DO NOT USE FOR: creating new extensions from scratch, or first-party extension…
openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
ce-optimize
Run metric-driven optimization loops. Use when improving a measurable outcome through experiments.
ce-pov
Give a decisive, project-grounded point of view: a graded verdict on an external-adoption question, a holistic take on a document, or a position on a supplied approach set. Use for a solo POV. Use when asked to consult other models, reconcile their opinions, or oracle. Not for findings review (use ce-doc-review)…