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 Knuckles-Team/repository-manager --skill repository-manager-concept-coordinationgit clone --depth 1 https://github.com/Knuckles-Team/repository-managerWrote 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/knuckles-team/repository-manager/repository-manager-concept-coordination)<a href="https://agentmods.dev/skills/knuckles-team/repository-manager/repository-manager-concept-coordination"><img src="https://agentmods.dev/badge/skills/knuckles-team/repository-manager/repository-manager-concept-coordination/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/knuckles-team/repository-manager/repository-manager-concept-coordination"><img src="https://agentmods.dev/badge/skills/knuckles-team/repository-manager/repository-manager-concept-coordination.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.00184 | $0.02046 |
| Opus 5 | $0.00092 | $0.01023 |
| Sonnet 5 | $0.00037 | $0.00409 |
| Haiku 4.5 | $0.00018 | $0.00205 |
Grade A, and why
repository-manager-concept-coordination 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 12d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Manager — Concept Coordination
rm_concepts is repository-manager's thin, MCP/CLI-neutral consumer of RMDD-16's
central concept-id claim authority (agent_utilities.governance. concept_reservation). Repository-manager never allocates a concept id itself —
every action here is a claim/verification call against an injected authority port.
⚠ Read this before anything else: the authority is unavailable on main today
As of this lane (verified 2026-08-10 against agent-packages/repository-manager
main at fdce825), RMDD-16's authority module is not an ancestor of
agent-utilities main. Every mutating rm_concepts action —
reserve/get/list/release/materialize/verify_candidate/verify_generation
— therefore refuses with a named ConceptAuthorityUnavailable refusal
(error_code: "dependency_blocked" from the shared RefusalCode/FailureClass
vocabulary), preserving the real ImportError as its cause. This is not a bug and
not this skill's cue to route around it:
- Never substitute a local, in-memory, or fixture allocator for the real
authority to "unblock" a demo —
repository_manager.concept_actions. build_default_concept_authority()is a deliberate best-effort probe that returnsNone(never a fabricated authority) whenever the module is absent, exposes no documented live-construction entrypoint, or construction itself raises. - Report the refusal truthfully —
{"ok": false, "refused": "...", "error_code": "dependency_blocked", "unreachable": ...}— rather than describing concept coordination as working. - This will change the moment RMDD-16's authority lands on agent-utilities
main; re-verify this section against the live server before trusting it stale.
When to use
- Before writing a new
CONCEPT:marker in code/docs, so two sessions never collide on the same identifier (reserve). - Checking or listing existing claims (
get/list). - Releasing a claim that was never actually used (
release). - Promoting a claim from reserved to in-use (
materialize). - Verifying one candidate's or one sealed generation's introduced
CONCEPT:markers against reserved claims, including cross-candidate collisions (verify_candidate/verify_generation). - A read-only drift report across the authority/fragment/view/source layers
(
reconcile).
What ships with it
2 files 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.
- 12d ago First seen · 150 lines · 184 tokens per session scan A 8b0a02596904
repository-manager-concept-coordination is a skill published in the GitHub repository Knuckles-Team/repository-manager (2 stars, last pushed 14d ago), licensed MIT. It adds 184 tokens to every session and 2,046 once invoked, about $0.0009 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-31.
Other skills, from other repositories
init-workspace-verification
Verify init completeness.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agentinsightsissue entities, offers to turn Diagnostics on when the project has it…
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
mcp-google-map-project
Project knowledge for developing and maintaining @cablate/mcp-google-map. Architecture, Google Maps API guide, GIS domain knowledge, and design decisions. Read this skill to onboard onto the project or make informed development decisions.