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/config-check)<a href="https://agentmods.dev/rules/bia-technologies/yaxunit/config-check"><img src="https://agentmods.dev/badge/rules/bia-technologies/yaxunit/config-check.svg" alt="Measured on agentmods" 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.00000 | $0.00847 |
| Opus 5 | $0.00000 | $0.00424 |
| Sonnet 5 | $0.00000 | $0.00169 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
config-check 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 6d 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
4 near-identical copies found in the catalogue:
- config-check — 100% identical, 0 lines differ
- config-check — 100% identical, 0 lines differ
- config-check — 100% identical, 0 lines differ
- config-check — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VAN QA: CONFIGURATION VALIDATION
TL;DR: This component validates configuration files for proper syntax and compatibility with the project and platform.
2️⃣ CONFIGURATION VALIDATION PROCESS
graph TD
Start["Configuration Validation"] --> IdentifyConfigs["Identify Configuration<br>Files"]
IdentifyConfigs --> ReadConfigs["Read Configuration<br>Files"]
ReadConfigs --> ValidateSyntax["Validate Syntax<br>and Format"]
ValidateSyntax --> SyntaxStatus{"Syntax<br>Valid?"}
SyntaxStatus -->|"Yes"| CheckCompatibility["Check Compatibility<br>with Platform"]
SyntaxStatus -->|"No"| FixSyntax["Fix Syntax<br>Errors"]
FixSyntax --> RetryValidate["Retry Validation"]
RetryValidate --> SyntaxStatus
CheckCompatibility --> CompatStatus{"Compatible with<br>Platform?"}
CompatStatus -->|"Yes"| ConfigSuccess["Configurations Validated<br>✅ PASS"]
CompatStatus -->|"No"| AdaptConfigs["Adapt Configurations<br>for Platform"]
AdaptConfigs --> RetryCompat["Retry Compatibility<br>Check"]
RetryCompat --> CompatStatus
style Start fill:#4da6ff,stroke:#0066cc,color:white
style ConfigSuccess fill:#10b981,stroke:#059669,color:white
style SyntaxStatus fill:#f6546a,stroke:#c30052,color:white
style CompatStatus fill:#f6546a,stroke:#c30052,color:white
Configuration Validation Implementation:
# Example: Validate configuration files for a web project
function Validate-Configurations {
$configFiles = @(
"package.json",
"tsconfig.json",
"vite.config.js"
)
$invalidConfigs = @()
$incompatibleConfigs = @()
foreach ($configFile in $configFiles) {
if (Test-Path $configFile) {
# Check JSON syntax for JSON files
if ($configFile -match "\.json$") {
try {
Get-Content $configFile -Raw | ConvertFrom-Json | Out-Null
} catch {
$invalidConfigs += "$configFile (JSON syntax error: $($_.Exception.Message))"
continue
}
}
# Specific configuration compatibility checks
if ($configFile -eq "vite.config.js") {
$content = Get-Content $configFile -Raw
# Check for React plugin in Vite config
if ($content -notmatch "react\(\)") {
$incompatibleConfigs += "$configFile (Missing React plugin for React project)"
}
}
} else {
$invalidConfigs += "$configFile (file not found)"
}
}
# Display results
if ($invalidConfigs.Count -eq 0 -and $incompatibleConfigs.Count -eq 0) {
Write-Output "✅ All configurations validated and compatible"
return $true
} else {
if ($invalidConfigs.Count -gt 0) {
Write-Output "❌ Invalid configurations: $($invalidConfigs -join ', ')"
}
if ($incompatibleConfigs.Count -gt 0) {
Write-Output "❌ Incompatible configurations: $($incompatibleConfigs -join ', ')"
}
return $false
}
}
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.
- 6d ago First seen · 103 lines · 0 tokens per session scan A b58ad6e3d5ea
config-check is a cursor rule published in the GitHub repository bia-technologies/yaxunit (324 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 847 tokens. 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
agent-working-memory
A system for keeping an AI agent's working information in files, including the plan, discoveries, decisions, and progress. It is intended for work that spans several tool calls or sessions.
testing-patterns
A set of rules and examples for testing 1C code with YaXUnit and Vanessa Automation. YaXUnit is used for unit tests of individual functions, while Vanessa Automation describes user scenarios as “given, when, then” steps.
zpa-dependency-chain
ZPA application onboarding requires resources to be created in a specific dependency order. Skipping dependencies causes cryptic 400 errors.
ivolgaql-parser-language
Project rules for building ИволгаQL, a query language and server that uses Russian commands and messages. They cover how new language features move through the lexer, parser, engine, and network protocol.
go
Cursor rule "go" from supertokens/create-supertokens-app, covering go and examples.
reference-repos
A rule containing related repositories for the namespace-forest project. A repository is a code project stored with its history and files.