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 skills add wahidyankf/ose-public --skill ci-standardsgit 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/skills/wahidyankf/ose-public/ci-standards)<a href="https://agentmods.dev/skills/wahidyankf/ose-public/ci-standards"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/ci-standards/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/skills/wahidyankf/ose-public/ci-standards"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/ci-standards.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.00027 | $0.00786 |
| Opus 5.5 | $0.00011 | $0.00314 |
| Sonnet 5.5 | $0.00005 | $0.00157 |
| Haiku 4.5 | $0.00003 | $0.00079 |
Grade A, and why
ci-standards 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Standards
Use the BDD standard, Nx targets, and CI conventions as canonical sources.
Project-Role Target Contract
- Every behaviour owner has real
test:unit,test:coverage:unit,test:coverage:behaviour, andtest:quicktargets. test:unitcollects native line coverage and hard-fails below 99%; dedicated E2E projects do not own Unit and never waive their source owner's threshold.- Add
test:integrationplustest:coverage:integrationonly for an owned real local-resource boundary. - Add E2E runtime/static coverage only for a public boundary. A dedicated E2E project implements its owner's corpus and does not invent Unit/Integration targets.
- Omit inapplicable targets. Echo/no-op/sentinel targets and compatibility aliases are violations.
test:coverageaggregates applicable static coverage validators. Every applicable validator is mandatory intest:quick.
Boundary and Execution Contract
Unit replaces every OS-facing dependency through injection; a shell script or harness plugin subject follows Script-Subject Unit Proof instead. Integration may use isolated local resources/processes plus a review-accepted loopback socket it owns, never an external network. E2E observes a real public browser, HTTP, or process boundary with synthetic isolated data.
Runtime test:* targets execute tests. Static test:coverage:* targets never execute or depend on
runtime tests. Pre-commit runs staged deterministic checks only. Pre-push runs affected quick
targets with --parallel=1; PR/main may use explicitly bounded shard parallelism. Neither runs
Integration/E2E runtime. Development/review runs impacted higher-layer scenarios manually;
scheduled or manually dispatched full-quality CI runs all static validators, complete Integration,
then complete unfiltered E2E.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 63 lines · 27 tokens per session scan A 1f1732600153
ci-standards is a skill published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 786 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 skills, from other repositories
fix-ci
Fix the failed CI checks for the current session. Use when the user requests a CI fix via the Fix Checks button in the Changes toolbar.
turborepo
Configure and troubleshoot Turborepo repositories. Use when working with turbo.json, task pipelines, caching, Remote Cache, the turbo CLI, filtering, environment variables, package boundaries, monorepo structure, or CI workflows.
tuturuuu-validation-offload
Run heavy Tuturuuu validation on an authorized devbox when local execution is unsuitable.
playwright-e2e-testing
Production-grade Playwright end-to-end testing skill for AI coding agents. Provides specialized guidance for writing, debugging, and maintaining Playwright tests in TypeScript, JavaScript, and Python. Covers the full testing lifecycle: test structure and architecture (Page Object Model, fixtures, custom matchers)…
modern-tooling
Opinionated tooling and conventions for modern JavaScript/TypeScript projects. Use when setting up new projects, configuring ESLint/Prettier, monorepos, library publishing, or establishing coding standards.
playwright-testing
E2E testing with Playwright - Page Objects, cross-browser, CI/CD.