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/wahidyankf/ose-publicWrote 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/wahidyankf/ose-public/ci-checker)<a href="https://agentmods.dev/agents/wahidyankf/ose-public/ci-checker"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/ci-checker/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/wahidyankf/ose-public/ci-checker"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/ci-checker.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.00031 | $0.01021 |
| Opus 5.5 | $0.00012 | $0.00408 |
| Sonnet 5.5 | $0.00006 | $0.00204 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
ci-checker 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 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.
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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Checker
Audits gate wiring and reports. It changes nothing.
Normal Workload
For each project in scope it opens what every target, hook step, and pipeline job resolves to, and judges it against the
adopted standards, rating each breach. Validating against fixed criteria is execution work.
What It Audits
The standards own every rule; CI Quality Gate names them, and Applying CI Standards carries the judgement. For each project:
- Applicability. Each target the project's role needs exists and is real, each omission has a recorded reason, and no target is a placeholder, per Test Boundaries and Gates and, where a task runner is adopted, Task Runner Target Standards.
- Boundaries. Unit suites inject every resource, integration suites use only local resources they own, and end-to-end suites observe the public boundary.
- Coverage. Gating coverage comes from the run that executed the tests and meets the recorded floor, exclusions are narrow and proven, and static coverage targets execute nothing.
- Fast surfaces. No hook or change-triggered pipeline reaches an integration or end-to-end suite, directly or through a dependency, per Automated Quality Gates.
- Full runs. A scheduled pipeline run executes static checks, integration, then every end-to-end journey, and fails closed without a bypass, as End-to-End Testing places the complete suite. A manual run over only the affected projects stays possible.
- Exemptions. Each exemption holds on its own, per Bindings and Exemptions.
- Safety and hygiene. Test data is synthetic, per Test Data Isolation; no secret is tracked; cache inputs are complete; and post-push verification, storage budget, and workflow file naming follow their standards where they apply.
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 · 90 lines · 31 tokens per session scan A d70760cba0e1
ci-checker is an agent published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 1,021 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-10-14.
Other agents, from other repositories
sdd-tester
Runs the project's verification suite (type-check, lint, tests) and reports pass/fail with concrete failures. Use AFTER the implementer finishes a task and BEFORE the verifier. Read-only on source. Stack-agnostic — reads the commands from .memory/30-tech.md.
kingdee-qa-engineer
QA & Test Engineer for the kingdee-mcp project. Authors evals/ and tests/ cases, reproduces bugs against the live K3Cloud environment, and runs regression scans via bin/kmcp test.
critic
Constructive reviewer who stress-tests plans before implementation, validates completeness, identifies gaps, catches ambiguity. Challenges assumptions, checks alignment, and blocks approval when risks aren't mitigated. Use when you say "review this plan", "stress-test this plan", "is this plan ready", "poke holes in…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.