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/jongio/skillsWrote 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/jongio/skills/session-statusline)<a href="https://agentmods.dev/rules/jongio/skills/session-statusline"><img src="https://agentmods.dev/badge/rules/jongio/skills/session-statusline/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/jongio/skills/session-statusline"><img src="https://agentmods.dev/badge/rules/jongio/skills/session-statusline.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.00237 | $0.00237 |
| Opus 5.5 | $0.00095 | $0.00095 |
| Sonnet 5.5 | $0.00047 | $0.00047 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
session-statusline 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 today.
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
Active session pills
When the session statusline tools are available, explicitly add an issue or PR
with session_issues or session_prs only when this session takes on its
implementation, review, repair, or active monitoring. All PR and issue enrollment
is explicit: shell commands, GitHub writes/results, and read-only lookups never
enroll targets automatically. Actual session agent launches are tracked automatically.
Never add pills for references, examples, attachments, memories, plans, search/list results, delegated prompts/results, or other sessions' work alone. Remove a target when this session stops working on it. Honor manual clear/remove: do not re-add an entry without new work or an explicit request.
Use the session-statusline skill for manual list/add/remove/clear/refresh requests.
Clearing pills must not close work, stop agents, delete transcripts or worktrees,
or change enabled components. Do not scan other sessions or edit raw tracking
files. If the extension tools are unavailable, do not claim tracking changed.
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.
- today First seen · 23 lines · 237 tokens per session scan A 93f72aed47fd
session-statusline is a cursor rule published in the GitHub repository jongio/skills (18 stars, last pushed today), licensed MIT. It adds 237 tokens to every session, about $0.0009 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-10-25.
Other cursor rules, from other repositories
feedback-enhanced
Rules for an interactive feedback system that lets users and an AI agent discuss complex development work in real time. It includes guidance for recording decisions, tracking progress and handling detailed inputs such as code and diagrams.
safeword-ticket-system
Ticket system and work logs for context anchoring during complex work. Use when creating tickets, managing work logs, referencing ticket IDs, or when work needs context anchoring (multi-step tasks, debugging, investigation).
revenue-architect
The local environment is optimized with rtk (Rust Token Killer). Always use the rtk prefix for shell commands (e.g., rtk npm test) to minimize token consumption.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.