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 repo-assessing-criticality-confidencegit 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/repo-assessing-criticality-confidence)<a href="https://agentmods.dev/skills/wahidyankf/ose-public/repo-assessing-criticality-confidence"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/repo-assessing-criticality-confidence/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/repo-assessing-criticality-confidence"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/repo-assessing-criticality-confidence.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.00086 | $0.00844 |
| Opus 5.5 | $0.00034 | $0.00338 |
| Sonnet 5.5 | $0.00017 | $0.00169 |
| Haiku 4.5 | $0.00009 | $0.00084 |
Grade A, and why
repo-assessing-criticality-confidence 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Criticality-Confidence System Skill
Purpose
This Skill provides comprehensive guidance on the criticality-confidence classification system used by all checker and fixer agents in the repository.
When to use this Skill:
- Implementing checker agents (categorizing findings)
- Implementing fixer agents (assessing confidence, determining priority)
- Processing audit reports
- Understanding priority execution order (P0-P4)
- Working with dual-label patterns (verification + criticality)
- Writing standardized audit reports
Core Concepts
See Core Concepts for the two orthogonal dimensions (criticality and confidence) and their four/three levels respectively.
Criticality × Confidence Priority Matrix
See Priority Matrix for the P0-P4 decision matrix and the fixer's strict execution order.
Checker Agent Responsibilities
See Checker Responsibilities for the criticality decision tree, the standardized audit report format, and the dual-label pattern (verification + criticality) used by five agents.
Fixer Agent Responsibilities
See Fixer Responsibilities for the re-validation process, confidence assessment steps, priority-based execution code patterns, and the fix report format.
False Positives and Domain-Specific Examples
See False Positives and Domain Examples for the false-positive report format and worked criticality examples across repo-governance, ayokoding-web, and documentation domains.
Common Patterns
See Common Patterns for three worked examples: checker categorizing a finding, fixer assessing confidence, and a dual-label finding.
Best Practices and Common Mistakes
See Best Practices and Common Mistakes for role-specific DO/DON'T guidance and the four most common classification mistakes.
What ships with it
12 files 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.
- README.md 667 B
- reference/best-practices-and-common-mistakes.md 1.6 KB
- reference/checker-responsibilities.md 3.3 KB
- reference/common-patterns.md 1.7 KB
- reference/core-concepts.md 2.2 KB
- reference/domain-examples-by-agent-family.md 1.8 KB
- reference/domain-examples-guidelines-and-notes.md 2.0 KB
- reference/domain-examples-purpose-and-template.md 1.5 KB
- reference/false-positives-and-domain-examples.md 1.9 KB
- reference/fixer-responsibilities.md 2.8 KB
- reference/priority-matrix.md 2.0 KB
- reference/README.md 1.3 KB
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 · 77 lines · 86 tokens per session scan A d7e4e0fbd644
repo-assessing-criticality-confidence is a skill published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 844 once invoked, about $0.0003 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
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.
nx-plugin-for-aws
Scaffold and build cloud-native applications on AWS using @aws/nx-plugin generators. Use when the user wants to create workspaces, generate projects, or scaffold infrastructure with the Nx Plugin for AWS.
frontmcp-setup
Use when starting, scaffolding, or organizing a FrontMCP project. Covers creating a new project (CLI scaffold or manual) for Node, Vercel, and other targets; standalone versus Nx-monorepo layout, naming conventions, generators, and dependency rules; composing multiple @App classes, ESM packages, and remote MCP servers…
investigate-cloudflare
Investigate deployed Worker failures, regressions, and missing operational signals using Cloudflare Issues, logs, traces, SQL, or Observability MCP. Produce bounded evidence and verify recurrence against the deployed version.
add-a-lib
Scaffold a new shared library under libs/ in the builders-stack monorepo. Use when code is needed in two or more places (apps or services) and should become a single source of truth consumed by package name. Covers the package.json, tsconfig, the one-public-door src/index.ts barrel, and wiring it into a consumer…
implement
Implement an agreed issue or spec through implementation, review, fixes, and a PR ready to merge.