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.
git clone --depth 1 https://github.com/Flomenco-Inc/flo-pluginWrote 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/rules/flomenco-inc/flo-plugin/session-start-current-state)<a href="https://agentmods.dev/rules/flomenco-inc/flo-plugin/session-start-current-state"><img src="https://agentmods.dev/badge/rules/flomenco-inc/flo-plugin/session-start-current-state/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/rules/flomenco-inc/flo-plugin/session-start-current-state"><img src="https://agentmods.dev/badge/rules/flomenco-inc/flo-plugin/session-start-current-state.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.00355 | $0.00355 |
| Opus 5.5 | $0.00142 | $0.00142 |
| Sonnet 5.5 | $0.00071 | $0.00071 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
session-start-current-state 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.
What it actually says
Session Start: Current State Assessment
Before writing any code in a new session, run this checklist. Present the results to the user as a status summary before proceeding.
Step 1 — Open PRs
gh pr list --repo Flomenco-Inc/flo-plugin --state open --author "@me" \
--json number,title,url,headRefName,reviewDecision \
--jq '.[] | "\(.number) \(.title) [\(.reviewDecision // "NONE")] \(.url)"'
If any open PRs exist:
- Failing CI → fix before starting new work.
- Unresolved review threads → reply and resolve before starting new work.
- Mergeable → merge now.
Do not start a new task while a previous PR is stalled.
Step 2 — Current branch and git state
git status --short
git branch --show-current
git log --oneline -5
Step 3 — Present the status summary
## Session Status
- Open PRs: <count> (<list with status>)
- Current branch: <branch> (<clean/dirty>)
- Blockers: <none, or list>
Architecture reference
This repo is the @flomenco/claude-plugin-mcp npm package. It connects to the flo API via OAuth. See flo/.cursor/rules/flo-system-architecture.mdc § "Claude plugin bootstrap + package" for how it integrates with the main system.
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 First seen · 45 lines · 355 tokens per session scan A 46374d507c7c
session-start-current-state is a cursor rule published in the GitHub repository Flomenco-Inc/flo-plugin (0 stars, last pushed 1mo ago), licensed MIT. It adds 355 tokens to every session, about $0.0014 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-08-31.
Other cursor rules, from other repositories
rebase-only-merged-agents
When rebasing after a merge, only rebase the agents whose branches you just merged. Do not rebase agents that are still running.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
git-workflow
Rules for git operations, commit strategy, and GitHub CLI usage.
release-checklist
What to update with each code change or version release.
git-workflow
Git commit format and PR process - conventional commits.
branching-merging-strategy
This is a set of instructions to the AI Assistant for branching and merging strategy.