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 bengous/claude-code-plugins --skill linear-flowgit clone --depth 1 https://github.com/bengous/claude-code-pluginsWrote 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/bengous/claude-code-plugins/linear-flow)<a href="https://agentmods.dev/skills/bengous/claude-code-plugins/linear-flow"><img src="https://agentmods.dev/badge/skills/bengous/claude-code-plugins/linear-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/bengous/claude-code-plugins/linear-flow"><img src="https://agentmods.dev/badge/skills/bengous/claude-code-plugins/linear-flow.svg" alt="Reviewed on agentmods" width="80" 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.00046 | $0.00685 |
| Opus 5 | $0.00023 | $0.00342 |
| Sonnet 5 | $0.00009 | $0.00137 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
linear-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 5d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear Flow
Doctrine for repos on the linear model. One linear signed history. dev is the working trunk. main is the release channel consumers use: a delayed pointer on dev's history, moved only by fast-forward. No merge commits anywhere; the server refuses them (required_linear_history).
dev ──●──●──●──●──●──●──●──► the only line of history
↑
main ───────────────┘ release = git push origin dev:main
main is always an ancestor of dev. If a repo has no release channel, main alone is the trunk and every dev rule below applies to main.
Rules
- Threshold. Small single-concern change: commit directly on
dev, atomic and curated. Big work (large feature, large skill), several concerns, or parallel agents: branch or PR stack targetingdev. - Landing. Rebase the branch on
dev, thengit push origin <branch>:dev. The identical SHAs reaching the base marks the PR merged. Never use the GitHub merge button: server-side merge or rebase re-creates commits unsigned and breaksrequired_signatures. - Release.
git push origin dev:mainwhendevhas soaked long enough. Nothing else ever touchesmain. - Force-push. Only on feature branches, only
--force-with-lease. Never ondevormain. - Review. Agents review other agents' PRs in fresh context. The human reviews contracts and runs tests at the end of a chantier and before each release; the human does not re-read details.
- History is authored. Curate commits before landing: atomic, conventional messages. Messy exploration gets squashed or reworded during the pre-land rebase, not after.
Recovery
| Symptom | Fix |
|---|---|
Push to dev/main rejected non-fast-forward |
Rebase on the current remote tip, push again. Never force. |
Push rejected required_linear_history |
A merge commit slipped in; rebase to flatten it, push again. |
| PR not marked merged after landing | The pushed SHAs differ from the PR head. Push the rebased branch to the PR first, then push it to dev. |
main no longer ancestor of dev |
Someone moved main off the line. Fast-forward the lagging ref onto the other; if truly diverged, stop and ask the user which line wins. |
git pull refused on dev |
Pull with rebase; the ruleset rejects merge commits from pulls too. |
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.
- 5d ago First seen · 41 lines · 46 tokens per session scan A 029236a6c4e7
linear-flow is a skill published in the GitHub repository bengous/claude-code-plugins (4 stars, last pushed 3d ago), licensed MIT. It adds 46 tokens to every session and 685 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-09-03.
Other skills, from other repositories
release
Verify, sweep docs, cut a version — then hand the release sequence back.
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
graincrawl
Maintain, verify, and release graincrawl, the local-first Granola archive CLI, including SQLite archive behavior, read-only Granola source boundaries, Homebrew tap packaging, and crawlkit-powered TUI/snapshot surfaces.
crawlkit
Maintain and release the crawlkit Go library, preserving downstream compatibility for gitcrawl, slacrawl, discrawl, and notcrawl.
release
Prepare code for release (version bumps, changelog, README updates) and create an annotated tag to trigger the GoReleaser workflow.
changelog-gen
Gerar CHANGELOG.md automatico a partir de commits e PRs entre tags/releases. Formato Keep a Changelog. Trigger quando usuario quer changelog, release notes, ou historico de mudancas.