Borrowing it
Nothing to install: this file belongs to dsheard/cobol-o-matic. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dsheard/cobol-o-matic/main/.claude/skills/repo-standards/SKILL.mdgit clone --depth 1 https://github.com/dsheard/cobol-o-maticWrote 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/dsheard/cobol-o-matic/repo-standards)<a href="https://agentmods.dev/skills/dsheard/cobol-o-matic/repo-standards"><img src="https://agentmods.dev/badge/skills/dsheard/cobol-o-matic/repo-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/dsheard/cobol-o-matic/repo-standards"><img src="https://agentmods.dev/badge/skills/dsheard/cobol-o-matic/repo-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.00038 | $0.00907 |
| Opus 5 | $0.00019 | $0.00453 |
| Sonnet 5 | $0.00008 | $0.00181 |
| Haiku 4.5 | $0.00004 | $0.00091 |
Grade A, and why
repo-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 11d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Standards
Tool / Workspace Separation
The tool (code, skills, templates) lives at the repository root. Analysis workspaces live in subdirectories or external paths.
cobol/ # Tool (code lives here)
├── analyse.py # Thin CLI entry point
├── orchestrator/ # Core Python package (config, agents, runner, cli, models, state, parser, stager)
├── prompts/ # Agent prompt builders (one per worker)
├── templates/ # Output artifact templates (frontmatter + sections)
├── examples/ # Reference configs for open-source COBOL apps
├── CLAUDE.md # Dev-focused (for IDE agent editing the tool)
└── README.md
workspace/ # Analysis workspace (agents run here)
├── config.yaml # Config: source paths, output dir, settings
├── CLAUDE.md # Agent-focused (output conventions)
├── source/ # COBOL input files
├── output/ # Generated markdown artifacts
├── staging/ # Chunked files for large programs
└── .cobol-re-state*.json # Orchestrator state files (auto-managed)
The orchestrator sets cwd to the workspace directory when spawning agents. Domain knowledge and template content are embedded directly in prompts by the orchestrator -- agents do not need to read external reference files.
Source Directory Configuration
Source paths are lists of directories in config.yaml, relative to the workspace. The tool scans all listed directories for files matching configured extensions.
| Type | Required | Extensions | Purpose |
|---|---|---|---|
programs |
Yes | .cbl, .cob, .CBL, .COB |
COBOL program source files |
copybooks |
Yes | .cpy, .copy, .CPY, .COPY |
Copybook include files |
jcl |
No | .jcl, .JCL, .prc, .PRC |
JCL jobs and procedures |
bms |
No | .bms, .BMS |
CICS BMS screen map definitions |
csd |
No | .csd, .CSD |
CICS CSD resource definitions |
sql |
No | .sql, .SQL |
SQL/DDL definitions |
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.
- 11d ago First seen · 69 lines · 38 tokens per session scan A 129a30ef1345
repo-standards is a skill published in the GitHub repository dsheard/cobol-o-matic (5 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 907 once invoked, about $0.0002 per session on Opus 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 skills, from other repositories
ile-cobol-docs
IBM ILE COBOL 7.4/7.5 — language structure, four divisions, data description, file handling, DB2, debugging.
mk:confluence-spec-analyst
Deep spec analysis on a Confluence page. Reads page (+ children) via the confluence-as wrapper, produces a structured Spec Research Report with requirements, acceptance criteria, gaps, ambiguities, and suggested user stories for human review. Read-only — does NOT create Jira tickets. Triggers: 'analyze spec for…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…