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-applying-maker-checker-fixergit 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-applying-maker-checker-fixer)<a href="https://agentmods.dev/skills/wahidyankf/ose-public/repo-applying-maker-checker-fixer"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/repo-applying-maker-checker-fixer/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-applying-maker-checker-fixer"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/repo-applying-maker-checker-fixer.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.00057 | $0.01076 |
| Opus 5.5 | $0.00023 | $0.00430 |
| Sonnet 5.5 | $0.00011 | $0.00215 |
| Haiku 4.5 | $0.00006 | $0.00108 |
Grade A, and why
repo-applying-maker-checker-fixer 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maker-Checker-Fixer Pattern (Comprehensive)
Complete guidance on the three-stage content quality workflow pattern used across repository agent families for systematic content creation, validation, and remediation.
Purpose
Use when implementing content quality workflows, working with maker/checker/fixer agents, validating content against conventions, applying validated fixes from audit reports, or creating new checker/fixer agents.
The Three Stages
Maker creates/updates content with cascading dependency management. Checker validates content against conventions and generates a criticality-categorized audit report (non-destructive). Fixer re-validates each finding, then applies only HIGH-confidence fixes, skipping MEDIUM and FALSE_POSITIVE for manual review.
See Stage 1: Maker and Stage 2 Checker Role for the Maker workflow and the Checker's role/criticality categories.
The Checker's 5-step process (Initialize → Validate → Finalize) is detailed in Checker Workflow: 5-Step Process and Checker Report Finalization and Progressive Writing.
The Fixer's 6-step process is detailed across Fixer Role, Priority, and Report Discovery, Fixer Mode Parameter Handling and Fix Application (lax/normal/strict/all), and Fix Report Structure and Trust Model (why fixers lack web tools).
Lifecycle-Owned Validation
Before any quality-gate checker, fixer, or recheck invocation, apply the canonical
lifecycle ownership Step 0.
Exclude registry-owned predicates from prompts and report them through lifecycle-status; keep
final-status domain-only.
Common Workflows and Agent Families
See Common Workflows and Agent Families for the basic and iterative maker→checker→fixer sequences and the repository-wide list of agent families using this pattern.
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 508 B
- reference/best-practices-and-common-mistakes.md 2.8 KB
- reference/checker-finalization.md 1.8 KB
- reference/checker-workflow-steps.md 3.8 KB
- reference/common-workflows-and-agent-families.md 1.4 KB
- reference/fixer-mode-and-application.md 2.6 KB
- reference/fixer-reporting-and-trust.md 2.6 KB
- reference/fixer-role-and-detection.md 3.8 KB
- reference/preventing-iteration-loops.md 3.6 KB
- reference/README.md 1.3 KB
- reference/stage1-maker-and-checker-role.md 2.7 KB
- reference/tool-requirements.md 893 B
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 · 70 lines · 57 tokens per session scan A fcb61a718ee3
repo-applying-maker-checker-fixer is a skill published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 1,076 once invoked, about $0.0002 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.