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/bia-technologies/yaxunitWrote 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/bia-technologies/yaxunit/optimized-workflow-level1)<a href="https://agentmods.dev/rules/bia-technologies/yaxunit/optimized-workflow-level1"><img src="https://agentmods.dev/badge/rules/bia-technologies/yaxunit/optimized-workflow-level1/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/bia-technologies/yaxunit/optimized-workflow-level1"><img src="https://agentmods.dev/badge/rules/bia-technologies/yaxunit/optimized-workflow-level1.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.01335 | $0.01335 |
| Opus 5.5 | $0.00534 | $0.00534 |
| Sonnet 5.5 | $0.00267 | $0.00267 |
| Haiku 4.5 | $0.00134 | $0.00134 |
Grade A, and why
optimized-workflow-level1 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- optimized-workflow-level1 — 100% identical, 0 lines differ
- optimized-workflow-level1 — 100% identical, 0 lines differ
- optimized-workflow-level1 — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OPTIMIZED LEVEL 1 WORKFLOW
TL;DR: This streamlined workflow for Level 1 tasks (quick bug fixes) optimizes for speed and token efficiency while maintaining quality.
🔧 LEVEL 1 PROCESS FLOW
graph TD
Start["START LEVEL 1<br>QUICK FIX"] --> Analyze["1️⃣ ANALYZE<br>Understand issue"]
Analyze --> Implement["2️⃣ IMPLEMENT<br>Fix the issue"]
Implement --> Verify["3️⃣ VERIFY<br>Test the fix"]
Verify --> Document["4️⃣ DOCUMENT<br>Record solution"]
style Start fill:#4da6ff,stroke:#0066cc,color:white
style Analyze fill:#ffa64d,stroke:#cc7a30,color:white
style Implement fill:#4dbb5f,stroke:#36873f,color:white
style Verify fill:#d94dbb,stroke:#a3378a,color:white
style Document fill:#4dbbbb,stroke:#368787,color:white
📝 CONSOLIDATED DOCUMENTATION
Level 1 tasks use a single-file approach to minimize context switching:
# QUICK FIX: [Issue Name]
## Issue Summary
- Type: [Bug/Hotfix/Quick Enhancement]
- Priority: [Low/Medium/High/Critical]
- Reported by: [Name/System]
- Affected area: [Component/Feature]
## Analysis
- Root cause: [Brief description]
- Affected files: [List of files]
- Impact: [Scope of impact]
## Solution
- Approach: [Brief description]
- Changes made: [List of changes]
- Commands executed: [Key commands]
## Verification
- Testing: [How the fix was tested]
- Results: [Test results]
- Additional checks: [Any other verification]
## Status
- [x] Fix implemented
- [x] Tests passed
- [x] Documentation updated
🔄 MEMORY BANK UPDATE
Level 1 tasks use a simplified Memory Bank update with minimal overhead:
## tasks.md Update (Level 1)
### Task: [Task Name]
- Status: Complete
- Implementation: [One-line summary]
- Link to fix: [File/line reference]
⚡ TOKEN-OPTIMIZED TEMPLATE
For maximum efficiency, Level 1 tasks can use this ultra-compact template:
## 🔧 FIX: [Issue]
📌 Problem: [Brief description]
🔍 Cause: [Root cause]
🛠️ Solution: [Implemented fix]
✅ Tested: [Verification method]
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 · 205 lines · 1,335 tokens per session scan A 72dcc59545f6
optimized-workflow-level1 is a cursor rule published in the GitHub repository bia-technologies/yaxunit (340 stars, last pushed 10d ago), licensed Apache-2.0. It adds 1,335 tokens to every session, about $0.0053 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-09-01.
Other cursor rules, from other repositories
running-tests
How to run tests, check for failures, and rerun specific failing tests — use the :agent variants of slow commands.
telegram-bot-tests
Test conventions for Telegram Bot library.
debug
Bug diagnosis and fixing standards - root cause analysis, minimal fixes, regression tests.
nodebench-auto-qa
Auto-QA after code changes using NodeBench MCP tools.
005-code-quality
Logging, error envelopes, testing coverage, performance conventions.
monitor-debug-shm
DEBUG /dev/shm full-message mirror — security, gating, and tests.