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/bernierllc/agents-environment-configWrote 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/bernierllc/agents-environment-config/workflow)<a href="https://agentmods.dev/rules/bernierllc/agents-environment-config/workflow"><img src="https://agentmods.dev/badge/rules/bernierllc/agents-environment-config/workflow/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/bernierllc/agents-environment-config/workflow"><img src="https://agentmods.dev/badge/rules/bernierllc/agents-environment-config/workflow.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.00883 | $0.00883 |
| Opus 5.5 | $0.00353 | $0.00353 |
| Sonnet 5.5 | $0.00177 | $0.00177 |
| Haiku 4.5 | $0.00088 | $0.00088 |
Grade A, and why
workflow 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 21d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Rules
Branching Strategy
Feature Branches
- Use feature branches for all new development
- Never commit directly to
mainorproduction - Always create feature branches from
main
Branch Naming Convention
Use this naming convention for feature branches:
{type}/{milestone-name}-{short-description}
Valid types:
feat: Featuresfix: Bugfixeschore: Maintenancerefactor: Refactoring
Examples:
feat/milestone3-invite-flowfix/milestone1-header-crashchore/infra-database-rotate
Syncing Before PR
Before opening a PR, ensure your feature branch is rebased on the latest main:
git fetch origin
git rebase origin/main
Commit Standards
Conventional Commit Format
Use conventional commit style for all commits:
<type>(<scope>): <description>
# Examples
feat(api): add user authentication endpoint
fix(port): resolve port conflict in development
docs(readme): update installation instructions
refactor(models): extract user validation logic
Commit Types
feat: New featurefix: Bug fixdocs: Documentation changesrefactor: Code refactoringtest: Adding or updating testschore: Maintenance tasksstyle: Code style changes (formatting, etc.)perf: Performance improvements
Commit Frequency
- Make commits for each feature/update
- Commit frequently with clear messages
- Group related changes in single commits
Pull Request Workflow
PR Flow
- Open the PR ready for review (not as a draft) once the work is complete
- Clearly describe:
- What is being changed
- Why it's needed
- Any relevant issue, milestone, or design doc
Requirements Before Merge
- ✅ Code review completed
- ✅ Tests pass
- ✅ Conflicts resolved (rebase preferred)
- ✅ Conventional commit title in squash merge
Merging
- Use Squash and Merge for feature branches
- The final commit message should be clean and follow conventional format
- PR title should follow conventional commit format
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.
- 21d ago Changed · +18 tokens per session 1965e297b1a3
- 1mo ago First seen · 137 lines · 865 tokens per session scan A 312143db3243
workflow is a cursor rule published in the GitHub repository bernierllc/agents-environment-config (11 stars, last pushed 9d ago), licensed MIT. It adds 883 tokens to every session, about $0.0035 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
beads
This project uses Beads (bd) for issue tracking.
safeword-pr-readiness
Prepare a pull request for human review and decide whether it may leave Draft. Use when creating or rewriting a PR description, marking a PR ready, responding to review, or checking mergeability.
review-workflow
Review, security, and commit workflow.
check
Analyze staged git changes with archguardian before committing.
custom-slash-commands
Enables custom slash commands, such as /commit, to generate conventional commit messages.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.