mainframe-project-harness

mainframe-project-harness is a skill for Claude Code, Codex from CATWILLgh/MAINFRAME. It costs 38 tokens per session (957 once invoked), scanned A, original, MIT.

A method for checking and maintaining the instructions and configuration that control coding assistants in a project. This includes rules, permissions, skills, hooks, commands, and tool connections.

In plain words
What is it for?
It helps inspect the effective assistant setup from a project root, identify conflicting instructions or settings, and establish or repair project configuration.
Why use it?
It reveals conflicts between global and project settings that can make an assistant behave unexpectedly. It can repair project-owned configuration when that is authorised.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps inspect the effective assistant setup from a project root, identify conflicting instructions or settings, and establish or repair project configuration.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/catwillgh/mainframe/mainframe-project-harness
Install

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.

Any agent
npx skills add CATWILLgh/MAINFRAME --skill mainframe-project-harness
Clone the repo
git clone --depth 1 https://github.com/CATWILLgh/MAINFRAME

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for mainframe-project-harness

README.md
[![agentmods](https://agentmods.dev/badge/skills/catwillgh/mainframe/mainframe-project-harness/github.svg)](https://agentmods.dev/skills/catwillgh/mainframe/mainframe-project-harness)
Your own site
<a href="https://agentmods.dev/skills/catwillgh/mainframe/mainframe-project-harness"><img src="https://agentmods.dev/badge/skills/catwillgh/mainframe/mainframe-project-harness/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.

agentmods 80×15 button for mainframe-project-harness

Your own site · 80×15
<a href="https://agentmods.dev/skills/catwillgh/mainframe/mainframe-project-harness"><img src="https://agentmods.dev/badge/skills/catwillgh/mainframe/mainframe-project-harness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 957 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.00957
Opus 5.5 $0.00015 $0.00383
Sonnet 5.5 $0.00008 $0.00191
Haiku 4.5 $0.00004 $0.00096

Measured 9d ago against content hash c37d6415e8b4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mainframe-project-harness 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 9d 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.

skills/mainframe-project-harness/SKILL.md · 92 lines

How it starts

The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Maintain the project harness

Start with the configuration implicated by the request or observed fault. Use current native tool contracts and established project evidence; consult official documentation when discovery, precedence, permissions, or reload behavior is uncertain or version-sensitive. Reuse current evidence already available.

Establish the effective harness

Read only the global configuration that can affect the project. Treat it as a preserved baseline and record its exact source and effect without changing it.

For a local repair, trace only the affected instruction chain and its owners. For an explicit project-wide harness audit, inventory discoverable components and inspect the relevant bodies, including:

  • root and nested instructions, overrides, and imports;
  • project settings and permissions;
  • skills and agent definitions;
  • hooks, commands, and workflows;
  • MCP declarations and tool policies, without reading secret values;
  • references, includes, symlinks, generated copies, and their canonical sources.

Reconstruct the actual chain from the global baseline through the project root to relevant subtrees. Distinguish always-loaded instructions from components loaded only when selected or invoked. Identify which source wins, where each rule applies, and which material is not discoverable.

Treat archives, backups, Trash, fixtures, caches, dependencies, and vendor trees as inactive unless documented discovery rules actually include them.

Surface conflicts proactively

Verify a suspected conflict against actual scope and precedence before reporting it. Do not manufacture a problem from harmless inheritance, intentional specialization, or wording that has the same effect.

When a real conflict or harness defect is found, report it proactively to the current recipient or your immediate caller. State:

  • the exact sources involved;
  • the effective behavior and why it wins;
  • the practical consequence for the current task or project;
  • the owner and correct edit location;
  • whether work can safely continue.

Read the full file on GitHub · 92 lines

Changes

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.

  1. 9d ago Changed · +11 tokens per session c37d6415e8b4
  2. 14d ago Changed · +15 lines · -80 tokens per session 5da0a54ca4eb
  3. 1mo ago First seen · 77 lines · 107 tokens per session scan A 43ac04f0fd4b

Subscribe to this mod's changes

mainframe-project-harness is a skill published in the GitHub repository CATWILLgh/MAINFRAME (2 stars, last pushed 3d ago), licensed MIT. It adds 38 tokens to every session and 957 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-09-08.