Borrowing it
Nothing to install: this file belongs to btspoony/mstar-harness. 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/btspoony/mstar-harness/main/AGENTS.mdgit clone --depth 1 https://github.com/btspoony/mstar-harnessWrote 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/instructions/btspoony/mstar-harness/agents-md)<a href="https://agentmods.dev/instructions/btspoony/mstar-harness/agents-md"><img src="https://agentmods.dev/badge/instructions/btspoony/mstar-harness/agents-md.svg" alt="Measured on agentmods" 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.04274 | $0.04274 |
| Opus 5 | $0.02137 | $0.02137 |
| Sonnet 5 | $0.00855 | $0.00855 |
| Haiku 4.5 | $0.00427 | $0.00427 |
Grade A, and why
mstar-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 4d 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Morning Star Harness Maintenance Guide
This repository is maintained as a harness/configuration project, not an application repo. Use this document as the primary maintenance contract for contributors and agents.
Scope
- Default intent in this workspace: maintain Morning Star harness behavior, docs, and host adapters.
- Repository layout uses a monorepo-style split:
packages/opencodefor the publishable OpenCode plugin (@mstar-harness/opencode),packages/cli(@mstar-harness/cli) for the standalone CLI. - Do not treat this repo like a product feature/codebase task unless explicitly requested.
- Runtime execution rules for users/agents live in
mstar-*skills; this file defines maintenance behavior.
Maintenance Goals
- Keep one coherent harness behavior across hosts.
- Keep prompts/rules minimal, explicit, and non-duplicated.
- Prefer stable defaults and small, reviewable changes.
- Preserve user safety boundaries for global config and secrets.
Core Rules
- Single source by topic: keep each rule in one authoritative place; avoid copy-paste rule drift.
- Execution vs maintenance split:
- Skills/role prompts describe runtime behavior.
AGENTS.mddescribes repository maintenance policy.
- Surgical edits: only change what the task requires; avoid opportunistic refactors.
- Read before edit: inspect current content before patching; verify after patching.
- Worktree-only development: all feature/plan development happens in git worktrees under
.worktrees/; the primary checkout stays onmainat all times. Never check out a working branch in the primary checkout — skills/commands may be symlinked into this directory, so a feature branch checked out here would break linked consumers. Localmainreceives no direct feature commits (changes land via PRs/merges). - README = developer consumer docs (
README.md/README_CN.md):- Audience is developers who install and run the harness — not a concept tutorial.
- Prefer commands, tables, and links. Do not write chatty “How to use” prose.
- A short curated value-prop bullet list at the top is allowed; keep it to a few selling points, not a marketing essay.
- Keep the shortest executable path: Install → Use (without iteration vs with iteration) → Workflow diagram → Roles/skills tables.
- Put narrative, deep install, and host quirks in
INSTALL.md,docs/, ormstar-*skills — not in the README body. - Edit both language files together when README content changes.
- Bilingual minimal updates: for paired docs (README.md/README_CN.md, packages/dsh README triplets), apply the minimal counterpart edit — never re-translate a document to apply an update — and re-record pairing hashes (
git hash-object) in the same change set.
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.
- 4d ago Changed · +4 lines · +101 tokens per session 3c701452562a
- 8d ago First seen · 253 lines · 4,173 tokens per session scan A 6397316781b7
mstar-harness AGENTS.md is an instructions file published in the GitHub repository btspoony/mstar-harness (58 stars, last pushed yesterday), licensed MIT. It adds 4,274 tokens to every session, about $0.0214 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.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.