agentmods.dev

better-harness AGENTS.md

Project instructions for QoderAI’s Better Harness, a cross-platform tool with a user interface, reports, and support for different coding-agent hosts. They define where architecture, design rules, and host-adapter guidance belong.

In plain words
What is it for?
Use them when changing the Harness Studio interface, architecture, reports, templates, or support for Windows, macOS, Linux, and new coding-agent hosts.
Why use it?
They give coding agents a shared map of the project and its visual rules, reducing inconsistent changes and misplaced documentation.

Instructions file for CodexOpenCode

2.1k +88 today A scan 2,535 tokens original MIT
View the source file QoderAI/better-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.

agentmods
npx agentmods add instructions/qoderai/better-harness/agents-md
Clone the repo
git clone --depth 1 https://github.com/QoderAI/better-harness

Made for: Codex, OpenCode.

Per session 2,535 This file is loaded in full into every session.
When invoked 2,535 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.02535 $0.02535
Opus 5 $0.01267 $0.01267
Sonnet 5 $0.00507 $0.00507
Haiku 4.5 $0.00253 $0.00253

Measured 2d ago against content hash 42fcab44d451, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

better-harness AGENTS.md 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.

AGENTS.md · 166 lines

How it starts

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

Better Harness

Cross-platform support is required (Windows, macOS, Linux). Architecture, directory routing, and template ownership live in docs/ARCHITECTURE.md. Adding support for a new Coding Agent host starts with docs/adapters/contributing-new-coding-agent.md.

UI and Visual Design

  • DESIGN.md is the visual source of truth for Harness Studio and interactive Better Harness reports unless a surface owns a narrower approved contract. Read it before changing UI hierarchy, typography, color, density, components, interaction states, or responsive behavior.
  • Keep AGENTS.md as the routing and enforcement layer; put reusable tokens, visual rationale, component rules, and do/don't guidance in DESIGN.md.
  • Treat Studio as a VS Code-inspired docked workbench: prefer panes, rows, tabs, toolbars, and editor views over cards, and define pointer and keyboard behavior before adding or changing an interaction.
  • Map Studio styles to shared semantic tokens. Do not introduce one-off colors, font sizes, radii, shadows, an unbundled font family, or broad !important overrides when the design contract already defines the role.
  • Visual review must prove the primary decision remains obvious at wide, compact, and narrow layouts. Verify keyboard focus, bounded overflow, browser console/page errors, and screenshots for every changed Studio surface.

Plan & Spec

  • Write a plan or spec for new agents, hooks, or major features under docs/specs/<yyyy-mm-dd>-<spec-name>.md, using the spec's creation date.
  • For non-trivial behavior changes to skills/, hooks/, scripts/, templates/, adapters, report formats, or review workflows, use .agents/skills/change-traceability-review/SKILL.md in Spec Preparation mode before implementation.
  • Prefer docs/specs/<yyyy-mm-dd>-<story-id>-<slug>.md when there is a Story or issue id; otherwise use docs/specs/<yyyy-mm-dd>-<slug>.md for justified maintenance, docs-only, test-only, dependency, or infra work.
  • Keep specs reviewable: include intent, acceptance scenarios with stable AC ids, non-goals, plan/tasks, and test/review evidence. Mark unknowns with [NEEDS CLARIFICATION: ...].
  • Keep docs/specs/*.md titles human-readable. Do not put Story ids, status, or review state in titles, and do not use YAML front matter by default.
  • Put traceability metadata in the body: Spec ID, optional Story, and Status in a short ## Traceability section.

Read the full file on GitHub · 166 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. 2d ago First seen · 166 lines · 2,535 tokens per session scan A 42fcab44d451

Subscribe to this mod's changes

better-harness AGENTS.md is an instructions file published in the GitHub repository QoderAI/better-harness (2,130 stars, last pushed today), licensed MIT. It adds 2,535 tokens to every session, about $0.0127 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-30.

agent-pluginclaude-codecodexcursorharness-designharness-engineering
Related

Other instructions, from other repositories

costwise-mcp AGENTS.md

Instructions for okyashgajjar/costwise-mcp, covering context for ai coding agents, v2 foundation (in progress — branch feat/v2-foundation), v3 enterprise capabilities (completed), cgo requirement and build & test.

okyashgajjar/costwise-mcp · 3,635 tokens

harness-workflow AGENTS.md

AGENTS.md instructions for YSAA1/harness-workflow, covering agents.md, 项目概览, 项目地图, 快速开始 and 项目铁律.

YSAA1/harness-workflow · 2,015 tokens

harness-workflow CLAUDE.md

Claude Code instructions for YSAA1/harness-workflow, a project described as: Context-aware agent workflow and project harness for Codex, Claude Code, and Cursor.

YSAA1/harness-workflow · 4 tokens

skills AGENTS.md

Instructions for qdrant/skills, covering qdrant skills, project overview, project structure, navigating skills locally and conventions.

qdrant/skills · 662 tokens

agentic-playwright selectors.instructions.md

Instructions for idavidov13/agentic-playwright, covering selector strategy, critical, instructions, phase 1: open and authenticate and phase 2: explore like a user.

idavidov13/agentic-playwright · 2,174 tokens

awesome-copilot-id AGENTS.md

Instructions for GulajavaMinistudio/awesome-copilot-id, covering communication, explanation and documentation, markdown formatting, user communication style and workflow & methodology.

GulajavaMinistudio/awesome-copilot-id · 7,686 tokens