Borrowing it
Nothing to install: this file belongs to jmrplens/gitlab-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jmrplens/gitlab-mcp-server/main/.github/skills/modularize-go-package/SKILL.mdgit clone --depth 1 https://github.com/jmrplens/gitlab-mcp-serverWrote 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/jmrplens/gitlab-mcp-server/modularize-go-package)<a href="https://agentmods.dev/skills/jmrplens/gitlab-mcp-server/modularize-go-package"><img src="https://agentmods.dev/badge/skills/jmrplens/gitlab-mcp-server/modularize-go-package/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/jmrplens/gitlab-mcp-server/modularize-go-package"><img src="https://agentmods.dev/badge/skills/jmrplens/gitlab-mcp-server/modularize-go-package.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.00065 | $0.04143 |
| Opus 5.5 | $0.00026 | $0.01657 |
| Sonnet 5.5 | $0.00013 | $0.00829 |
| Haiku 4.5 | $0.00006 | $0.00414 |
Grade A, and why
modularize-go-package 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 16d 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 — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modularize Go Package
Primary Directive
Transform a monolithic Go package into a modular structure with domain-specific sub-packages and a shared utilities package. Every step must maintain compilation and test integrity.
Execution Model
This skill operates in atomic migration batches. Each batch moves one domain to its own sub-package. Between batches, the project must compile and all tests must pass. Never move to the next batch until the current one is verified.
Prerequisites
Before invoking this skill, ensure:
- Clean git working directory (
git statusshows no uncommitted changes) - All tests pass:
go test ./internal/... -count=1 - All code compiles:
go build ./... - You have identified the source package and its domain files
Input Parameters
${sourcePackage}— The monolithic package to modularize (e.g.,internal/tools)${utilPackage}— Name for the shared utilities package (e.g.,internal/toolutil)${domains}— Comma-separated list of domains to extract (e.g.,branches,commits,issues)
Process
Step 1: Inventory Analysis
Scan the source package and classify every file:
| Category | Files | Action |
|---|---|---|
| Shared utilities | errors.go, pagination.go, logging.go, markdown.go, text.go, meta_tool.go, string_or_int.go, file_utils.go, time_helpers.go | Extract to ${utilPackage} |
| Shared constants | Annotation variables, format constants | Extract to ${utilPackage} |
| Domain handlers | branches.go, commits.go, etc. | Move to ${sourcePackage}/{domain}/ |
| Domain tests | branches_test.go, commits_test.go, etc. | Move with their domain |
| Test helpers | helpers_test.go | Extract to internal/testutil (exported NewTestClient, RespondJSON, RespondJSONWithPagination) |
| Catalog wiring | action_specs.go, catalog aggregation | Keep runtime surfaces catalog-backed; do not add package-level meta registration as the final path |
| Package doc | (doc comment in any file) | Create ${sourcePackage}/doc.go |
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.
- 16d ago Changed 80b365b27ae0
- 23d ago Changed b1363df67e8c
- 1mo ago Changed 3d47a590a398
- 1mo ago Changed 70556aeb35e6
- 1mo ago Changed · -1 lines 61d4caaea0f7
- 1mo ago Changed 26ab07087b28
- 1mo ago First seen · 346 lines · 65 tokens per session scan A 3b2e69ea525f
modularize-go-package is a skill published in the GitHub repository jmrplens/gitlab-mcp-server (46 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 4,143 once invoked, about $0.0003 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
goai
GoAI is a Go SDK for AI applications. One unified API across 25+ LLM providers. Inspired by the Vercel AI SDK, adapted to Go idioms (generics, interfaces, channels).
golang-benchmark
Run reproducible Go benchmarks, profiling, benchstat and CI regression analysis.
golang-observability
Instrument Go services using slog, OpenTelemetry, Prometheus and profiling.
go-expert
Expert-level Go development with Go 1.22+ features, concurrency, standard library, and production-grade best practices. Use when the user mentions concurrency, microservices, or backend, or when the task involves idiomatic Go, goroutines and channels, context-based cancellation, or writing an HTTP server.
go-code-review
Use when reviewing Go code or checking code against community style standards. Also use proactively before submitting a Go PR or when reviewing any Go code changes, even if the user doesn't explicitly request a style review. Does not cover language-specific syntax — delegates to specialized skills.
go-concurrency
Use when writing concurrent Go code — goroutines, channels, mutexes, or thread-safety guarantees. Also use when parallelizing work, fixing data races, or protecting shared state, even if the user doesn't explicitly mention concurrency primitives. Does not cover context.Context patterns (see go-context).