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/J-Pster/Psters_AI_WorkflowWrote 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/j-pster/psters_ai_workflow/commits)<a href="https://agentmods.dev/rules/j-pster/psters_ai_workflow/commits"><img src="https://agentmods.dev/badge/rules/j-pster/psters_ai_workflow/commits/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/j-pster/psters_ai_workflow/commits"><img src="https://agentmods.dev/badge/rules/j-pster/psters_ai_workflow/commits.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.00337 | $0.00337 |
| Opus 5.5 | $0.00135 | $0.00135 |
| Sonnet 5.5 | $0.00067 | $0.00067 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
commits 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
Commit Messages
- ALWAYS write commit messages in English
- Use conventional commit format with emojis when appropriate
- Preferred format with ticket:
[TICKET-XXXX] <emoji> <type>(<scope>): <subject> - Allowed format without ticket:
<emoji> <type>(<scope>): <subject>
Commit Types
🚀 feat: New feature🐛 fix: Bug fix📝 docs: Documentation changes♻️ refactor: Code refactoring✅ test: Adding or updating tests⚡ perf: Performance improvements🔧 chore: Maintenance tasks🎨 style: Code style changes (formatting, etc.)🔒 security: Security fixes🚧 wip: Work in progress
Examples
🚀 feat(auth): add JWT authentication🐛 fix(api): resolve CORS configuration issue📝 docs: update README with deployment instructions♻️ refactor(users): improve service structure✅ test: add unit tests for auth service⚡ perf(database): optimize query performance[TICKET-1234] 🚀 feat(auth): add JWT authentication(optional ticket prefix)
Guidelines
- Keep subject line under 50 characters when possible
- Use imperative mood ("add" not "added" or "adds")
- First line should be a summary
- Add detailed description in body if needed (separated by blank line)
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 · 42 lines · 337 tokens per session scan A 0a906230a116
commits is a cursor rule published in the GitHub repository J-Pster/Psters_AI_Workflow (289 stars, last pushed 7mo ago), licensed MIT. It adds 337 tokens to every session, about $0.0013 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-30.
Other cursor rules, from other repositories
workflow
Git branching strategy, commit conventions, and pull request workflow.
atomic-commits
Git best practices - atomic commits, descriptive messages, feature branches.
quality-gates
Enforce quality checks before commits - lint, typecheck, and test affected code.
beads
This project uses Beads (bd) for issue tracking.
phase-summary
Always run the phase-summary skill before proposing any commit that completes a task loop.
git
Git workflow — commit format, push policy, and PR process.