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/gmickel/flow-next/flow-next-prosenpx skills add gmickel/flow-next --skill flow-next-prosegit clone --depth 1 https://github.com/gmickel/flow-nextWrote 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/gmickel/flow-next/flow-next-prose)<a href="https://agentmods.dev/skills/gmickel/flow-next/flow-next-prose"><img src="https://agentmods.dev/badge/skills/gmickel/flow-next/flow-next-prose.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.00042 | $0.00307 |
| Opus 5 | $0.00021 | $0.00153 |
| Sonnet 5 | $0.00008 | $0.00061 |
| Haiku 4.5 | $0.00004 | $0.00031 |
Grade A, and why
flow-next-prose 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 6d 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
Flow Prose
Ambient triggering is host-discretionary on every host: the host matches this skill's description at the moment the agent begins drafting a substantial reply.
The agent reads the prose contract at docs/prose.md, resolved relative to this SKILL.md file's own location. If the doc is absent, the skill proceeds without it and never blocks the reply.
The agent applies the contract's rules 1-10 at draft time and writes the reply under them from the first draft.
The reply-dormant parts of the doc are the precedence section's dedup-marker and projection bullets, which stay idle for replies. Rule 8 (user-outcome-first ordering) softens to lead with the answer. Rule 10 (honesty) stays fully active.
The agent never rewrites quoted material, code, or command output, and never restyles the user's words where they are being quoted back. A draft the user hands the skill as the /flow-next:prose <draft> argument is submitted for tightening, so the agent rewrites it under the contract.
Pass the identity (the path above). Never copy rule text from the doc into this skill.
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.
- 6d ago First seen · 21 lines · 42 tokens per session scan A 2e6110252e7f
flow-next-prose is a skill published in the GitHub repository gmickel/flow-next (691 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 307 once invoked, about $0.0002 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
project-execution
Executes implementation plans with progress tracking, checkpoint validation, and quality gates. Use after planning is complete and tasks are ready to implement.
pr
Comprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue.
backlog
Read, work, and maintain a Git repo's deferred-work items in docs/backlog/, one file per item. Use when the user says "backlog", "check backlog", "what's on my backlog", "work the backlog", "address the backlog", "add to backlog", "clean up backlog", or when a review or task produced items that are real but not being…
ask-codex
Consult OpenAI Codex for investigation, debugging, or code review. Use when user explicitly asks to "ask codex", "check with codex", "codex review", or as a last resort when stuck after 4+ failed attempts at debugging, investigation, or bug fix and completely out of ideas. Codex is slow (2-5 min), so only escalate…
clarify
This skill should be used when user appears confused, frustrated, or shows misalignment between expectations and reality. Triggers on phrases like "I don't understand", "this doesn't make sense", "confused", "wait, shouldn't it...", "why is this happening", "I thought X did Y", contradictory statements, or frustration…
writing-style
Use for technical communication - GitHub/GitLab tickets, PR/MR descriptions, issue comments, code review comments, commit messages. Direct, brief style with no AI-speak. NOT for README.md, public docs, or blog posts.