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-operationsgit 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-operations)<a href="https://agentmods.dev/skills/knuckles-team/repository-manager/repository-manager-operations"><img src="https://agentmods.dev/badge/skills/knuckles-team/repository-manager/repository-manager-operations/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-operations"><img src="https://agentmods.dev/badge/skills/knuckles-team/repository-manager/repository-manager-operations.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.00083 | $0.00355 |
| Opus 5 | $0.00042 | $0.00178 |
| Sonnet 5 | $0.00017 | $0.00071 |
| Haiku 4.5 | $0.00008 | $0.00036 |
Grade A, and why
repository-manager-operations 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 10d 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.
This is a copy
80% identical to gitlab-api-operations — 11 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Repository Manager Operations
Use the provider's governed MCP tools through GraphOS delegation.
Workflow
- Establish the verified GraphSession and tenant before discovery or retrieval.
- Discover the current condensed tool surface; never assume a stale tool name or schema.
- Prefer read-only inspection first. For changes, present impact and use the provider's dry-run or preview mode when available.
- Execute mutations as fenced WorkItems so retries remain idempotent and auditable.
- Ingest source data only through the signed connector preset and ChangeEnvelope path.
- Verify the durable result and its trace/evidence before reporting completion.
Safety contract
- Never persist credentials, endpoints, raw personal identifiers, hostnames, or local paths.
- Resolve TLS trust and verification from environment/configuration; never hardcode bypasses.
- Treat unknown ACL, tenant, schema, or tool-contract state as a hard failure.
- Require explicit approval for destructive, externally visible, or irreversible actions.
- Keep runtime traces policy-scoped and privacy-sanitized.
Specialized workflows
Read the workflow catalog only when the request needs a provider-specific procedure, parameter map, script, or reference asset.
What ships with it
3 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.
- 10d ago First seen · 39 lines · 83 tokens per session scan A c5ae2342c890
repository-manager-operations is a skill published in the GitHub repository Knuckles-Team/repository-manager (2 stars, last pushed 13d ago), licensed MIT. It adds 83 tokens to every session and 355 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 80% identical to gitlab-api-operations, differing in 11 lines, and is treated as a copy.
Other skills, from other repositories
release-changelog-harness
Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable. Use for release CI, install.sh, versioning, CHANGELOGs, shipping MCP/CLI without clone, or meta repos that only ship skills via npx…
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
github-via-nyxid
Operate a user's GitHub account through NyxID's credential-brokering proxy (service slug api-github) — read and write repositories, files, issues, pull requests, commits, branches, Actions, gists and anything else the GitHub REST API exposes, all on the user's behalf and without ever handling a raw token. NyxID…
git-workflow
Git best practices for version control and collaboration.
memory-commit
Use when the user explicitly says "remember this", "save this", "ghi nho", "luu lai", "save for next time", or otherwise asks to persist the immediately preceding context. Captures with the appropriate contexttype (decision, preference, fact, skill, task, conversation) so future sessions can retrieve it accurately.
p4-stream-workflows
P4 stream workflows — creation, branching, merging, copying, integration, switching, and spec management via P4 MCP tools. Use when: creating streams, branching, merging, copying between streams, integrating changes, switching workspaces, or managing stream specs in P4.