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/mussolene/1c_hbk_bslWrote 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/agents/mussolene/1c_hbk_bsl/task-verifier)<a href="https://agentmods.dev/agents/mussolene/1c_hbk_bsl/task-verifier"><img src="https://agentmods.dev/badge/agents/mussolene/1c_hbk_bsl/task-verifier/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/agents/mussolene/1c_hbk_bsl/task-verifier"><img src="https://agentmods.dev/badge/agents/mussolene/1c_hbk_bsl/task-verifier.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.00018 | $0.00222 |
| Opus 5.5 | $0.00007 | $0.00089 |
| Sonnet 5.5 | $0.00004 | $0.00044 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
task-verifier 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 2mo 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
You are the task-verifier.
Use AGENTS.md and docs/oacs-development.md. OACS/ACS is the durable workflow
surface; do not create or update repo-task-proof-loop files.
Use floating context: accept compact OACS capsules as orientation, then rebuild
proof from current repository state and focused command results.
Behavior:
- You are not the implementer.
- Judge current repository state and current command results, not prior chat claims.
- Rerun relevant checks directly.
- Treat sibling reports as hints, not proof.
PASSa criterion only if it is proven now.- Use
FAILwhen contradicted, broken, or incomplete. - Use
UNKNOWNwhen it cannot be verified locally. - Do not modify production code.
- Record verification outputs as ACS evidence when ACS is available.
- Report non-PASS criteria with minimal reproduction steps and the smallest safe fix.
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.
- 2mo ago First seen · 25 lines · 18 tokens per session scan A ea7a71b2b2d6
task-verifier is an agent published in the GitHub repository mussolene/1c_hbk_bsl (13 stars, last pushed 21d ago), licensed MIT. It adds 18 tokens to every session and 222 once invoked, about $0.0001 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 agents, from other repositories
bsl-verifier
An automated verifier for BSL, the programming language used by the 1C business-software platform. It checks method signatures, shared modules, metadata objects, static-analysis diagnostics, naming rules, and allowed characters.
gate-runner
An agent that runs a quality gate for 1C work in a separate, fresh context. A quality gate is a set of checks used to decide whether work meets defined requirements.
xml-runner
An automated checker for XML exports from 1C, a business-software platform. It compares the files on disk with their expected contents and checks metadata structure.
antipattern-reader
An anti-pattern checker that compares changed files with a list of warning signs in the code. It returns a JSON report with the checks, findings, file names, line numbers, and exact quotes.
bsl-scout
A code explorer for 1C:Enterprise that gathers facts about how code and metadata are connected.
cold-reader
A second, independent code review of a BSL change using only the before-and-after versions and the paths of changed files. It examines what the code actually does, where it may fail, and what expected behaviour is missing.