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.
npx skills add monoes/monomind --skill mastermind-techportgit clone --depth 1 https://github.com/monoes/monomindWrote 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/monoes/monomind/mastermind-techport)<a href="https://agentmods.dev/skills/monoes/monomind/mastermind-techport"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-techport/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/monoes/monomind/mastermind-techport"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-techport.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.00036 | $0.09451 |
| Opus 5.5 | $0.00014 | $0.03780 |
| Sonnet 5.5 | $0.00007 | $0.01890 |
| Haiku 4.5 | $0.00004 | $0.00945 |
Grade A, and why
mastermind-techport 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.
How it starts
The opening of the file, as written. The whole thing — 775 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mastermind TechPort
Five-phase porting skill. Phases 0–1 run in parallel. Phase 2 builds the gap matrix. Phase 3 produces the port plan and is the confirm gate (STOP — wait for user approval). Phase 4 is pre-execution setup (snapshot + secrets check). Phase 5 executes with full mono branding normalization.
Standalone Execution
If invoked directly (not by mastermind:master):
- Load brain context following
mastermind-protocol/SKILL.mdBrain Load Procedure (namespace:techport) - Parse
source_path,focus_hint,modefrom user input - Proceed with Phase 0 below
- At the end of every run — regardless of which phase concluded — execute
mastermind-protocol/SKILL.mdBrain Write Procedure, writing output to namespacemastermind:techport:raw. This includes Phase 1A license-gate STOPs and secrets STOPs. Never skip Brain Write.
Inputs
source_path: absolute or relative path to the foreign project rootfocus_hint: optional — what to look for ("CLI commands", "animation", "hooks", "skills"); default:"core architecture skills commands hooks agents"mode: confirm | autopartial: boolean — if true, skip strategy (a) Copy-As-Is; force (b) Adapt or (c) Extract onlysource_brand: derived in Phase 1A — PascalCase brand name of the source project (e.g.Monomind,ClaudeFlow); used in allrg -i "{source_brand}"brand contamination checkscandidate_file: derived during Phase 1E–1F — absolute path to a specific source file under analysis; substituted before running per-candidate coupling checks
Phase 0 — Target (Monomind) Deep Review
Run before looking at the source project. This establishes what already exists, what naming conventions are enforced, and what architectural constraints must not be violated.
Steps 0B–0D run in parallel with Phase 1. Phase 0A runs first in sequence.
0A — Existing Capability Inventory
Step 1 — check index freshness, rebuild only if stale (must complete before Step 2):
Call mcp__monomind__monograph_health({})
IF health.commitsBehind > 0 OR health.status != "fresh":
Call mcp__monomind__monograph_build({ codeOnly: true })
// monograph_build runs in the background. Poll freshness by re-calling monograph_health
// every ~10s until health.status == "fresh" or health.commitsBehind == 0, then proceed to Step 2.
// If index is already fresh, skip monograph_build and proceed directly to Step 2
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.
- 2d ago First seen · 775 lines · 36 tokens per session scan A 2c46bd69f616
mastermind-techport is a skill published in the GitHub repository monoes/monomind (23 stars, last pushed 2d ago), licensed Apache-2.0. It adds 36 tokens to every session and 9,451 once invoked, about $0.0001 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-10-26.
Other skills, from other repositories
compare-harnesses
Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.
create-harness
Scaffold your own focused AI agent harness — pick host (Claude Code, Codex, pi.dev, Hermes), template, agents, skills, and ship a npm-publishable harness with its own npx CLI. Use when a user asks to "create my own agent harness", "scaffold a harness", "make a custom Claude Code plugin like ruflo", or "build a…
diag-harness
Kernel-version skew check (ADR-027). Reports manifest surface + manifest kernel + installed kernel + verdict (match/patch-diff/minor-diff/major-diff). Exits 1 on minor/major skew with a copy-pasteable npm install @metaharness/[email protected] next step. Exits 2 if no .harness/manifest.json at path.
example-harness
Scaffold a ready-made AI agent harness in one command from the 19 published @metaharness/ example packages — 9 host integrations (Claude Code, Codex, Hermes, pi.dev, OpenClaw, RVM, Copilot, OpenCode, GitHub Actions) + 10 vertical pods (devops, research, trading, support, legal, coding, education, sales, gaming…
oia-manifest
Emit .harness/oia-manifest.json declaring layer alignment with the OIA v0.1 9-layer reference architecture. Self-describes the harness's MCP wiring, witness signing, audit log, identity posture (always 'none' at v0.1). --check verifies an existing manifest, --dry-run prints without writing, --json emits to stdout.
repo-genome
7-section readiness scorecard for a LOCAL repo. Reports repo type + agent topology + MCP risk + test confidence + release readiness + recommended harness plan + scorecard. Exit 0 ready, 1 needs-work, 2 blocked. --json for the 6-field scorecard, --bundle for the ADR-031 schema-1 envelope.