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 Guepard-Corp/gfs --skill use-gfs-mcpgit clone --depth 1 https://github.com/Guepard-Corp/gfsWrote 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/guepard-corp/gfs/use-gfs-mcp)<a href="https://agentmods.dev/skills/guepard-corp/gfs/use-gfs-mcp"><img src="https://agentmods.dev/badge/skills/guepard-corp/gfs/use-gfs-mcp/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/guepard-corp/gfs/use-gfs-mcp"><img src="https://agentmods.dev/badge/skills/guepard-corp/gfs/use-gfs-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00030 | $0.03669 |
| Opus 5.5 | $0.00012 | $0.01468 |
| Sonnet 5.5 | $0.00006 | $0.00734 |
| Haiku 4.5 | $0.00003 | $0.00367 |
Grade A, and why
use-gfs-mcp 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 24d 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 — 490 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GFS MCP Server
GFS provides an MCP (Model Context Protocol) server for AI agent integration, enabling programmatic access to database version control operations including commits, branches, time travel, and schema versioning.
Supported Databases
- PostgreSQL (versions 13-18)
- MySQL (versions 8.0-8.1)
- SQLite (version 3) — file-based; needs no container runtime
With SQLite, init, commit, log, status, checkout, extract_schema,
show_schema, diff_schema, export_database, import_database and query
all work with no container runtime running. compute and user do not apply:
there is no server to start and no roles to manage.
Installation
1. Verify GFS CLI is installed
The MCP server requires the GFS CLI to be installed on the host system.
2. Configure MCP Server
Add GFS to your MCP client configuration (e.g., Claude Desktop, custom MCP client). The MCP server runs as: gfs mcp
Configuration requires:
- Command: Path to
gfsbinary - Args:
["mcp"] - Optional:
GFS_REPO_PATHenvironment variable
Quick Start
1. Start MCP Server
The server starts automatically when configured in your MCP client. It provides access to all GFS operations through MCP tools.
2. Check Available Tools
The MCP server exposes 14 tools for database version control operations. All tools accept an optional path parameter to specify repository location.
3. Verify Repository Status
Use the status tool to check repository state, current branch, HEAD commit, and database container status.
Revision References
GFS supports Git-style revision notation in all tools that accept commit references (checkout, show_schema, diff_schema, log):
Basic Formats
HEAD- Current commitmain- Branch tip (any branch name)abc123def456...- Full commit hash (64 characters)
Tilde Notation (Ancestor References)
Reference ancestor commits using ~ notation:
HEAD~1- Parent of HEAD (previous commit)HEAD~5- 5th ancestor of HEADmain~3- 3 commits before main branch tipabc123~2- 2nd parent of commit abc123HEAD~- Same asHEAD~1(defaults to 1)
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.
- 24d ago Changed · +27 lines 7ee005f42720
- 1mo ago First seen · 463 lines · 30 tokens per session scan A 7907fcb6d60f
use-gfs-mcp is a skill published in the GitHub repository Guepard-Corp/gfs (160 stars, last pushed 9d ago), licensed MIT. It adds 30 tokens to every session and 3,669 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-30.
Other skills, from other repositories
sql-knowledge
Comprehensive SQL Server and T-SQL development knowledge for queries, stored procedures, and database optimization. Use when working with: (1) T-SQL query writing and optimization, (2) Stored procedure development, (3) Execution plan analysis and indexing, (4) Window functions, CTEs, PIVOT, MERGE, APPLY, (5)…
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
pipeline-conductor
Operating procedure for the kirocrew-pipeline-conductor agent. Use when a pipeline conductor session is seeded, inspected or debugged. You MANAGE one issue/PR pipeline on one repo: two columns per item (session working? item solved?), send intent, never re-derive a red yourself.
release-notes
Create release notes for a new version tag. Gathers all commits, PRs, issues fixed, and breaking changes since a previous release. Creates the release notes markdown file, tags the repo, and pushes. Asks the user to confirm the base version to diff against.
release-notes
Draft a release note section from a commit range, grouped by what the reader gets.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.