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/Yuhamixli/Law-Crawler-RPA-RAG-MCPWrote 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/yuhamixli/law-crawler-rpa-rag-mcp/002-development-workflow)<a href="https://agentmods.dev/rules/yuhamixli/law-crawler-rpa-rag-mcp/002-development-workflow"><img src="https://agentmods.dev/badge/rules/yuhamixli/law-crawler-rpa-rag-mcp/002-development-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/yuhamixli/law-crawler-rpa-rag-mcp/002-development-workflow"><img src="https://agentmods.dev/badge/rules/yuhamixli/law-crawler-rpa-rag-mcp/002-development-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.00217 | $0.00217 |
| Opus 5 | $0.00109 | $0.00109 |
| Sonnet 5 | $0.00043 | $0.00043 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
002-development-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 10d 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
Development Workflow Rules
Code Quality Standards
- Always include error handling and input validation
- Write clear, self-documenting code with meaningful variable names
- Include appropriate comments for complex logic
- Follow language-specific best practices and conventions
File Organization
- Use consistent naming conventions across the project
- Organize files in logical directory structures
- Keep related files grouped together
- Maintain a clean project root directory
Git Workflow
- Make small, focused commits with descriptive messages
- Include issue numbers in commit messages when applicable
- Use semantic commit messages (feat:, fix:, docs:, etc.)
- Always test code before committing
Documentation
- Keep README.md updated with current setup instructions
- Document API endpoints and their usage
- Include examples for complex functionality
- Maintain changelog for significant updates
Development Environment
- Use consistent development tools across team members
- Include necessary configuration files in version control
- Document environment setup requirements
- Use package managers for dependency management
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.
- 10d ago First seen · 37 lines · 217 tokens per session scan A 96d4087427fe
002-development-workflow is a cursor rule published in the GitHub repository Yuhamixli/Law-Crawler-RPA-RAG-MCP (31 stars, last pushed 4mo ago), licensed MIT. It adds 217 tokens to every session, about $0.0011 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-08-30.
Other cursor rules, from other repositories
git-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.
skill-management
A repository rule for managing coding-agent skills across their source files, generated copies, and version lock file. It treats third-party skills as part of the project’s tracked behavior contract.
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.
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.
git-workflow
Rules for git operations, commit strategy, and GitHub CLI usage.
release-checklist
What to update with each code change or version release.