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 ofershap/mcp-server-github-gist --skill gist-managementgit clone --depth 1 https://github.com/ofershap/mcp-server-github-gistWrote 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/ofershap/mcp-server-github-gist/gist-management)<a href="https://agentmods.dev/skills/ofershap/mcp-server-github-gist/gist-management"><img src="https://agentmods.dev/badge/skills/ofershap/mcp-server-github-gist/gist-management/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/ofershap/mcp-server-github-gist/gist-management"><img src="https://agentmods.dev/badge/skills/ofershap/mcp-server-github-gist/gist-management.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.00034 | $0.00394 |
| Opus 5.5 | $0.00014 | $0.00158 |
| Sonnet 5.5 | $0.00007 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
gist-management 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 1mo 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.
What it actually says
GitHub Gist Management via MCP
Use this skill when you need to create, read, update, or manage GitHub Gists. Fills the gap the official GitHub MCP server leaves for Gists.
Available Tools
| Tool | What it does |
|---|---|
gist_list |
List your gists (paginated) |
gist_get |
Get a gist by ID (includes file contents) |
gist_create |
Create a new gist (public or secret) |
gist_update |
Update description or file contents |
gist_delete |
Delete a gist |
gist_starred |
List your starred gists |
gist_star |
Star a gist |
gist_unstar |
Unstar a gist |
Workflow
gist_createto save code snippets — specifypublic: falsefor secret gists (default)gist_listto browse existing gistsgist_getwith a gist ID to read file contentsgist_updateto modify description or files
Key Patterns
- Gists are secret by default — pass
public: truefor publicly discoverable gists gist_createaccepts multiple files — useful for multi-file snippetsgist_getreturns full file contents — use it to read existing gist code- Requires
GITHUB_TOKENwith thegistscope
Safety
- Confirm before
gist_delete— deletions are permanent - Secret gists are accessible by URL but not searchable — they're not truly private
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.
- 1mo ago First seen · 41 lines · 34 tokens per session scan A 1f0b777f2957
gist-management is a skill published in the GitHub repository ofershap/mcp-server-github-gist (2 stars, last pushed 7mo ago), licensed MIT. It adds 34 tokens to every session and 394 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-08-31.
Other skills, from other repositories
publish-release
Releases a new McpOrchestrator version end to end — version bump PR, tag, and the automated deploy to GitHub Releases, NuGet, and the MCP Registry. Use when asked to release, publish, deploy, ship, or bump the version of McpOrchestrator.
feedback-nudge
Use when the user wants to report a bug, request a feature, or send feedback to the Zooza engineering team. Also offer proactively after a successful commit operation (max once per week).
release-notes
Writes user-facing release notes from a git commit range. Use when asked to draft release notes, a changelog entry, or "what's new" text for a release.
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…