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-secretsgit 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-secrets)<a href="https://agentmods.dev/skills/monoes/monomind/mastermind-secrets"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-secrets/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-secrets"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-secrets.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.00041 | $0.01755 |
| Opus 5.5 | $0.00016 | $0.00702 |
| Sonnet 5.5 | $0.00008 | $0.00351 |
| Haiku 4.5 | $0.00004 | $0.00176 |
Grade A, and why
mastermind-secrets scanned grade A with 2 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- `local`: `.monomind/orgs/.secrets/<org_name>/<name>` (chmod 600, gitignored) Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -H "Authorization: Bearer $secret" ... How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mastermind Secrets
This skill is invoked directly via /mastermind-secrets.
Bookkeeping only — not enforced by the Org Runtime. It writes .monomind/orgs/<org>-secrets.json and .monomind/orgs/.secrets/<org>/, which no runtime code reads: org agents never receive these values.
Inputs
brain_context: BRAIN CONTEXT blockorg_name: org to manage secrets foraction: list | set | rotate | revoke | auditsecret_name: name/key of the secret (e.g.OPENAI_API_KEY,SLACK_WEBHOOK)secret_value: value to store (only ever passed as env var reference, NEVER hardcoded)provider: local | env | vault (default: local)caller: command | master
Step 0 — Brain Load (standalone only)
If caller is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: ops.
SECURITY RULES (always enforced)
- NEVER print secret values to stdout
- NEVER store secret values in state files (store only masked references:
sk-ant-***...***) - NEVER commit secrets to git
- Secrets passed as
secret_valueMUST come from env vars ($MY_KEY), NOT inline strings
Step 1 — Load Secrets Registry
The secrets registry stores metadata only (name, provider, masked hint, rotation date):
secretsFile=".monomind/orgs/${org_name}-secrets.json"
[ ! -f "$secretsFile" ] && echo '{"secrets":[]}' > "$secretsFile"
Actual secret values live in:
local:.monomind/orgs/.secrets/<org_name>/<name>(chmod 600, gitignored)env: environment variableORG_<ORG_NAME_UPPER>_<SECRET_NAME_UPPER>
Step 2 — Execute Action
list (default)
Show all registered secrets for this org (metadata only, masked values):
jq -r '
(.secrets // [])[] |
"[\(.name)] provider=\(.provider) hint=\(.masked_hint // "***") set=\(.set_at // "unknown") rotated=\(.rotated_at // "never")"
' "$secretsFile" 2>/dev/null || echo "No secrets registered."
Render as:
SECRETS — org: <org_name>
──────────────────────────────────────────────
NAME PROVIDER VALUE HINT SET ROTATED
ANTHROPIC_API_KEY local sk-ant-***... 2 days ago —
SLACK_WEBHOOK env https://hooks 1 week ago —
GITHUB_TOKEN local ghp_***... 3 days ago 1 day ago
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 · 203 lines · 41 tokens per session scan A 0ff1f5828c3f
mastermind-secrets is a skill published in the GitHub repository monoes/monomind (23 stars, last pushed 2d ago), licensed Apache-2.0. It adds 41 tokens to every session and 1,755 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 2 findings (asks for root, makes network calls). 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.