Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mrvladd-d/memobanknpx agentmods add skills/mrvladd-d/memobank/mb-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/skills/mrvladd-d/memobank/mb-harness)<a href="https://agentmods.dev/skills/mrvladd-d/memobank/mb-harness"><img src="https://agentmods.dev/badge/skills/mrvladd-d/memobank/mb-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.
<a href="https://agentmods.dev/skills/mrvladd-d/memobank/mb-harness"><img src="https://agentmods.dev/badge/skills/mrvladd-d/memobank/mb-harness.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.00024 | $0.00863 |
| Opus 5 | $0.00012 | $0.00432 |
| Sonnet 5 | $0.00005 | $0.00173 |
| Haiku 4.5 | $0.00002 | $0.00086 |
Grade A, and why
mb-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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mb-harness — Harness engineering setup
- What it does: defines the execution harness around the repo, including commands, gates, and parallel-safe workflow.
- Use it when: the repository needs stronger agent guardrails before autonomous or multi-session work.
- Input: repository root and the project’s canonical build, test, and lint commands.
- Output: documented quality gates, optional Codex config, and a safer harness for agent execution.
Goal
Turn the repo into a reliable “harness” for agents:
- clear entry points (AGENTS.md)
- reproducible commands (build/test/lint)
- mechanical checks (CI + MB lint)
- parallel-safe workflow (worktrees)
Process
1) Codex project configuration (optional but recommended)
If you use Codex:
- Create
.codex/folder. - Create
.codex/config.tomlfromassets/codex-config.toml.
Usage examples:
- default profile (coding):
codex - deep review:
codex --profile deep-review
2) Document quality gates
In AGENTS.md (keep it short), list the canonical commands (examples):
- install deps
- lint / typecheck
- unit tests
- e2e tests
If the repo has UI or browser flows, explicitly document:
- Playwright command(s)
- agent-browser / browser MCP path (if available)
- where screenshots/videos/traces are stored
- which flows are considered release-critical
If the repo lacks them, add minimal scripts/Make targets.
3) Worktree workflow (parallel agents)
If multiple agents work in parallel:
- create worktrees per agent to avoid file conflicts
- merge only after passing gates
Example:
git worktree add ../wt-agent-1 -b agent-1
4) Add deterministic Memory Bank gates
If not already present, install the packaged Memory Bank gate assets:
scripts/mb-lint.mjsfrommb-garden/assets/mb-lint.mjsscripts/mb-doctor.mjsfrommb-garden/assets/mb-doctor.mjs- CI workflow coverage for the default health gates
The mb-garden/assets path is the current packaged asset location, not conceptual ownership of the doctor role. mb-lint covers structural/mechanical hygiene. mb-doctor covers workflow/autonomous readiness over mb-lint. Run default mb-doctor for ordinary pre-queue health checks. Run strict mode only after the JSON task queue exists: after /prd-to-tasks, before scheduler execution inside /autonomous, or before /autopilot when the queue is already prepared:
What ships with it
1 file 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.
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.
- 9d ago First seen · 88 lines · 24 tokens per session scan A 8bbc195a6fec
mb-harness is a skill published in the GitHub repository mrvladd-d/memobank (55 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 863 once invoked, about $0.0001 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 skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.