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/bia-technologies/yaxunit/common-fixesgit clone --depth 1 https://github.com/bia-technologies/yaxunitWhat 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.00000 | $0.00825 |
| Opus 5 | $0.00000 | $0.00413 |
| Sonnet 5 | $0.00000 | $0.00165 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade B, and why
common-fixes scanned grade B with 1 finding 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 2d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
| **Permission denied** | Run terminal as administrator (Windows) or use sudo (Mac/Linux) | Copies of this mod
3 near-identical copies found in the catalogue:
- common-fixes — 100% identical, 0 lines differ
- common-fixes — 100% identical, 0 lines differ
- common-fixes — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VAN QA: COMMON VALIDATION FIXES
TL;DR: This component provides common fixes for issues that may arise during the QA validation process.
🧪 COMMON QA VALIDATION FIXES BY CATEGORY
Dependency Issues
| Issue | Fix |
|---|---|
| Missing Node.js | Download and install Node.js from https://nodejs.org/ |
| Outdated npm | Run npm install -g npm@latest to update |
| Missing packages | Run npm install or npm install [package-name] |
| Package version conflicts | Adjust versions in package.json and run npm install |
| Dependency resolution issues | Run npm cache clean -f and try installing again |
Configuration Issues
| Issue | Fix |
|---|---|
| Invalid JSON | Use a JSON validator (e.g., jsonlint) to check syntax |
| Missing React plugin | Add import react from '@vitejs/plugin-react' and plugins: [react()] to vite.config.js |
| Incompatible TypeScript config | Update tsconfig.json with correct React settings |
| Mismatched version references | Ensure consistent versions across configuration files |
| Missing entries in config files | Add required fields to configuration files |
Environment Issues
| Issue | Fix |
|---|---|
| Permission denied | Run terminal as administrator (Windows) or use sudo (Mac/Linux) |
| Port already in use | Kill process using the port: netstat -ano | findstr :PORT then taskkill /F /PID PID (Windows) or lsof -i :PORT then kill -9 PID (Mac/Linux) |
| Missing build tools | Install required command-line tools (git, node, etc.) |
| Environment variable issues | Set required environment variables: $env:VAR_NAME = "value" (PowerShell) or export VAR_NAME="value" (Bash) |
| Disk space issues | Free up disk space, clean npm/package cache files |
Build Test Issues
| Issue | Fix |
|---|---|
| Build fails | Check console for specific error messages |
| Test fails | Verify minimal configuration is correct |
| Path issues | Ensure paths use correct separators for the platform (\ for Windows, / for Mac/Linux) |
| Missing dependencies | Make sure all required dependencies are installed |
| Script permissions | Ensure script files have execution permissions (chmod +x on Unix) |
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.
- 2d ago First seen · 92 lines · 0 tokens per session scan B 3e50ad19bce6
common-fixes is a cursor rule published in the GitHub repository bia-technologies/yaxunit (322 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 825 tokens. A static security scan graded it B with 1 finding (asks for root). 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
ktnip-ksp-processor
KSP processor architecture, collectors, and codegen for ktnip.
1c-coding-standards
Стандарты кода BSL: именование, запросы, коллекции.
edt-form-xml-requirements
Требования EDT к XML-формам (Form.form): extInfo, дефолты полей.
1c-skd-two-pass-preprocessing
Двухпроходный СКД: предобработка детальных записей до свертки.
1c-form-reserved-names
Зарезервированные имена свойств в модулях форм 1С.
agent-working-memory
Рабочая память агента: файлы плана, передача сессии, журнал инцидентов.