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/hamzaamjad/cursor-rulesWrote 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/hamzaamjad/cursor-rules/427-stigmergic-workflows-optimized)<a href="https://agentmods.dev/rules/hamzaamjad/cursor-rules/427-stigmergic-workflows-optimized"><img src="https://agentmods.dev/badge/rules/hamzaamjad/cursor-rules/427-stigmergic-workflows-optimized/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/hamzaamjad/cursor-rules/427-stigmergic-workflows-optimized"><img src="https://agentmods.dev/badge/rules/hamzaamjad/cursor-rules/427-stigmergic-workflows-optimized.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.00005 | $0.00380 |
| Opus 5.5 | $0.00002 | $0.00152 |
| Sonnet 5.5 | $0.00001 | $0.00076 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
427-stigmergic-workflows-optimized 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
Stigmergic Workflow Patterns
Purpose: Enable coordination through environmental traces rather than direct communication.
Core Implementation
Environmental Markers
- Status comments:
TODO(category): description→ classify work state - File naming:
feature_WIP_username.tsx→ broadcast progress - Decision trails:
// DECIDED: approach X because Y→ document rationale
Adaptive Signals
- Performance hotspots accumulate profiling markers
- Success patterns strengthen through repetition
- Warning indicators emerge at failure points
Artifact Communication
# .workflow-state.yaml
current_phase: implementation
blockers: [api_design]
decisions:
- choice: REST over GraphQL
rationale: latency requirements
evidence: benchmarks/api-comparison.json
Self-Organization Rules
- Auto-index directories when files > 20
- Promote patterns used > 10x to recommended
- Cluster related work via naming proximity
Validation
- Context discovery < 30 seconds
- State inferable from environment alone
- Conflict rate reduction measurable
Integration
- Version control: Branch names as signals
- CI/CD: Pipelines respond to state markers
- Scaling: More valuable with team size
External patterns: @notepads/400-patterns/stigmergic-examples.md
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 · 59 lines · 5 tokens per session scan A c1aee28189d6
427-stigmergic-workflows-optimized is a cursor rule published in the GitHub repository hamzaamjad/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It adds 5 tokens to every session and 380 once invoked, about $0.0000 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
slice-tasks
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
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.
elite-orchestrator
Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).
sprint-planning
BMAD BMM Agent: sprint-planning.