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 chemany/Mente --skill mente-config-admingit clone --depth 1 https://github.com/chemany/MenteWrote 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/chemany/mente/mente-config-admin)<a href="https://agentmods.dev/skills/chemany/mente/mente-config-admin"><img src="https://agentmods.dev/badge/skills/chemany/mente/mente-config-admin.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.00040 | $0.02120 |
| Opus 5 | $0.00020 | $0.01060 |
| Sonnet 5 | $0.00008 | $0.00424 |
| Haiku 4.5 | $0.00004 | $0.00212 |
Grade A, and why
mente-config-admin 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mente Config Admin
Overview
Use this skill for user-facing operational changes to Mente itself: changing API keys, rotating provider credentials, updating config.yaml, fixing gateway platform tokens, or restarting the gateway after a config change.
This is not a general coding skill. It is an operational playbook for safely modifying live Mente configuration without breaking the current install, profile, or executor auth flow.
When to Use
- The user says things like:
- "帮我改 API key"
- "把 OpenRouter key 换掉"
- "改一下模型配置"
- "重登 Codex"
- "修改 Feishu/Slack/微信 token"
- "改 gateway 配置"
- "改
.env/config.yaml" - "改 Mente 的登录态"
- The task touches provider auth, gateway auth, model provider selection, platform secrets, or restart behavior.
- The user wants Mente to perform the change directly instead of just explaining it.
Do not use this skill for ordinary application code changes inside a user project.
Core Rule
Always classify the request first. These targets are different:
| Target | Canonical storage | Normal action |
|---|---|---|
| API keys / tokens / secrets | effective HERMES_HOME/.env |
Edit .env |
| Non-secret settings | effective HERMES_HOME/config.yaml |
Edit config.yaml |
| OAuth / device-code auth state | effective HERMES_HOME/auth.json |
Prefer mente model, mente auth, mente logout; do not hand-edit unless forced |
| Skills / skill state | MENTE_HOME/skills/ |
Not part of ordinary key rotation |
Two names exist in the codebase:
get_hermes_home()is still the effective runtime home for config, auth, gateway state, logs, and.env.get_mente_home()is the separate Mente-owned home used for skills and some executor-specific assets.
Do not guess which root is active. Resolve the real paths first.
Resolve Paths First
Before editing anything, resolve the active config files from the running install:
mente config path
mente config env-path
If you need to inspect the effective homes directly:
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 First seen · 264 lines · 40 tokens per session scan A 50be4e9b7688
mente-config-admin is a skill published in the GitHub repository chemany/Mente (11 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 2,120 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…