Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/parvez3019/go-swagger3npx agentmods add skills/parvez3019/go-swagger3/claudeWrote 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/parvez3019/go-swagger3/claude)<a href="https://agentmods.dev/skills/parvez3019/go-swagger3/claude"><img src="https://agentmods.dev/badge/skills/parvez3019/go-swagger3/claude/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/parvez3019/go-swagger3/claude"><img src="https://agentmods.dev/badge/skills/parvez3019/go-swagger3/claude.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 222 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Agent Snooping · line 12 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium MCP Rug Pull · line 23 Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.Fix: Pin the image: image:tag or image@sha256:abc123
- low Tool Misuse · line 23 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00063 | $0.03413 |
| Opus 5 | $0.00032 | $0.01707 |
| Sonnet 5 | $0.00013 | $0.00683 |
| Haiku 4.5 | $0.00006 | $0.00341 |
Grade A, and why
go-swagger3-docs 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 9d 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 — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
go-swagger3 — document existing Go APIs
Copy this file into a consumer project as .claude/skills/go-swagger3-docs/SKILL.md.
Annotate existing Go code with go-swagger3 godoc @ tags and struct tags, then run the CLI. Prefer editing comments and tags over rewriting handlers.
Install
go install github.com/parvez3019/go-swagger3@latest
export PATH="$HOME/go/bin:$PATH"
# Docker alternative
docker run -t --rm -v $(pwd):/app -w /app parvez3019/go-swagger3:latest \
--module-path . --main-file-path ./cmd/api/main.go --output oas.json --schema-without-pkg
Workflow
- Confirm
go.modexists (Go modules only). - Put service annotations on the main/entry file (
@Titleand@Versionrequired). - Annotate each HTTP handler’s godoc (comments must sit directly above the func).
- Add
json+ OAS tags on request/response structs; add@Enum/@HeaderParameterstypes when needed. - Generate (pick the matching layout):
# main next to go.mod go-swagger3 --module-path . --output oas.json --schema-without-pkg # main elsewhere go-swagger3 --module-path . --main-file-path ./cmd/api/main.go --output oas.json --schema-without-pkg # only scan handlers under a path go-swagger3 --module-path . --main-file-path ./cmd/api/main.go --handler-path ./internal/handlers --output oas.json --schema-without-pkg # YAML go-swagger3 --module-path . --main-file-path ./cmd/api/main.go --output oas.json --schema-without-pkg --generate-yaml - Open the output, fix gaps, re-run with
--debugif needed. Use--strictwhen hardening.
CLI flags
| Flag | Purpose |
|---|---|
--module-path |
Module root to scan |
--main-file-path |
File with service-level annotations |
--handler-path |
Optional: only scan handlers under this path |
--output |
Output path (default oas.json) |
--schema-without-pkg |
Schema names without package prefix |
--generate-yaml |
Emit YAML (.json output becomes .yml) |
--exclude |
Comma-separated dirs to skip |
--quiet |
Reduce log noise |
--debug |
Debug logging |
--strict |
Treat parse warnings as fatal |
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.
- 9d ago First seen · 348 lines · 63 tokens per session scan A 6970bea468b4
go-swagger3-docs is a skill published in the GitHub repository parvez3019/go-swagger3 (149 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 3,413 once invoked, about $0.0003 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-30.
Other skills, from other repositories
cartograph-use-case
Compile use-case trees into docs/hops.md: Input → Branches → Output. Use when hops.md is missing or stale, the user asks to map a flow, an event is a different use case, or traces break across async calls.
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
vellum-oauth-integrations
Act on behalf of your user in any third-party software that supports OAuth 2.0.
openapi-expert
OpenAPI/Swagger expert for API specification design, validation, and code generation.
architecture-decision-record
ADR templates in the Nygard format with context, decision, consequences, and alternatives. Use when writing ADRs, recording an architectural decision, or evaluating options.
search-suitable-public-api
Search the curated Agenvoy public API list for an API that fits the current user need or skill context, then chain into the api-tool-add skill to register it under /.config/agenvoy/tools/api/. Triggers when the agent lacks a tool for a data lookup (weather, currency, geocoding, dictionary, etc.), when the user says…