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.
git clone --depth 1 https://github.com/spf13/go-skillsWrote 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/plugins/spf13/go-skills/fileflow-pathologize)<a href="https://agentmods.dev/plugins/spf13/go-skills/fileflow-pathologize"><img src="https://agentmods.dev/badge/plugins/spf13/go-skills/fileflow-pathologize/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/plugins/spf13/go-skills/fileflow-pathologize"><img src="https://agentmods.dev/badge/plugins/spf13/go-skills/fileflow-pathologize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
fileflow-pathologize 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- fileflow-pathologize — 100% identical, 0 lines differ
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "fileflow-pathologize",
"displayName": "File Operations: fileflow & pathologize",
"description": "Safe file operations in Go using spf13/fileflow (move, copy, rename across filesystems with conflict-safe naming) and spf13/pathologize (make filenames and path segments safe on every OS).",
"version": "1.0.0",
"author": {
"name": "Steve Francia",
"email": "[email protected]"
},
"homepage": "https://github.com/spf13/go-skills",
"repository": "https://github.com/spf13/go-skills",
"license": "MIT",
"keywords": ["go", "golang", "files", "fileflow", "pathologize"]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 151 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 16 lines scan A 9d6354624b95
fileflow-pathologize is a plugin published in the GitHub repository spf13/go-skills (677 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
jwx-dev-v4
Guide for developing Go applications with github.com/lestrrat-go/jwx v4 — parse and sign JWTs, work with JWS/JWE/JWK, pick algorithms, and avoid common footguns.
go-ultimate
Opinionated Go development skill — architecture, conventions, production readiness, repo/CI hygiene, review, and MCP/agent patterns.
golang-skills
20 modular skills for idiomatic Go — each under 225 lines, backed by 48 reference files, 8 automation scripts (all with --json, --limit, --force), and 4 asset templates. Covers error handling, naming, testing, concurrency, interfaces, generics, documentation, logging, performance, and more. Activates automatically…
claude-go
Go language support: goimports auto-formatting on file edits, Go coding conventions.
go-standards
Stdlib-grounded Go engineering standards for implementation, review, refactoring, and testing.
aio-golang-mastery
Write and lint idiomatic Go end-to-end — a 7-tool lint chain (build, vet, golangci-lint, govulncheck, nilaway, deadcode, race) plus reference-grade patterns for concurrency, errors, generics, gRPC, naming/style enforcement (revive 21-rule set, golangci-lint v2 production config), and production hardening.