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.
npx agentmods add rules/andurilcode/accordo/execute-tasksgit clone --depth 1 https://github.com/AndurilCode/accordoWhat 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 | $0.01528 | $0.01528 |
| Opus 5 | $0.00764 | $0.00764 |
| Sonnet 5 | $0.00306 | $0.00306 |
| Haiku 4.5 | $0.00153 | $0.00153 |
Grade A, and why
execute-tasks 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 yesterday.
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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Execution Guidelines
🚨 MANDATORY WORKFLOW COMPLIANCE 🚨
Before starting ANY task, evaluate it using these criteria:
Use Workflow Tools When:
- Task involves multiple steps or phases
- Task requires coordination across multiple files
- Task involves creating, modifying, or analyzing code structures
- Task requires planning, analysis, or systematic approach
- Task involves debugging, testing, or validation
- Task creates new features, components, or systems
- When in doubt, ALWAYS use workflows
Only Skip Workflows For:
- Single mathematical calculations
- One-line explanations or definitions
- Direct copy/paste operations
- Immediate answers to factual questions
🔍 SESSION AWARENESS & WORKFLOW DISCOVERY
⚠️ MANDATORY PRE-WORKFLOW CHECK: Before starting ANY new workflow, check for existing sessions:**
STEP 0: CHECK EXISTING SESSIONS (REQUIRED FIRST STEP)
workflow_cache_management(operation="list")
Purpose: Check for existing workflow sessions to avoid conflicts and enable session resumption Results:
- Active Session Found & Applicable: Resume existing workflow using its session_id
- Active Session Found & NOT Applicable: Start new workflow for current task
- No Active Sessions: Proceed to workflow discovery
- Multiple Sessions: Choose appropriate session, complete irrelevant ones, or start new
Session Applicability Assessment:
Before resuming any existing session, verify:
- Is the existing workflow relevant to the current task?
- Are you continuing the same work or starting something different?
- If the task is different or unrelated → START NEW WORKFLOW
Session Resumption Pattern:
If existing session found AND applicable to current task, resume with:
workflow_guidance(session_id="found-session-id", action="next", context='{"choose": "current_node"}')
Session Conflict Resolution:
If multiple active sessions exist:
- Check session status with
workflow_cache_management(operation="list") - Evaluate session relevance to current task
- CRITICAL: Only resume if directly related to current task
- If unrelated: Complete or abandon existing sessions and start new workflow
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.
- yesterday First seen · 170 lines · 1,528 tokens per session scan A 5f71ec4bea02
execute-tasks is a cursor rule published in the GitHub repository AndurilCode/accordo (5 stars, last pushed 10mo ago), licensed MIT. It adds 1,528 tokens to every session, about $0.0076 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-31.
Other cursor rules, from other repositories
api-property-optionality-hygiene
Fix ApiProperty/ApiPropertyOptional optionality mismatches in DTO files; use for scheduled batch fixes or DTO edits.
java-springboot-jpa-cursorrules-prompt-file
description: "Cursor rules for Java development with Springboot and JPA integration." globs: / alwaysApply: false.
conservative-file-creation
Check for existing files before creating. Be conservative about new files and code.
secure-dev-rust
These rules apply to all Rust code in the repository and aim to prevent common security risks through disciplined use of memory safety, input validation, error handling, and safe APIs.
design-patterns
Design patterns (GoF) and file size conventions for sweagent TypeScript codebase.
cursorrules
ALWAYS start your session by reading AGENTS.md and .memory/wiki/hot.md to get project context before suggesting code or answering questions.