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 soulcodex/agentic --skill golang-manual-digit clone --depth 1 https://github.com/soulcodex/agenticWrote 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/soulcodex/agentic/golang-manual-di)<a href="https://agentmods.dev/skills/soulcodex/agentic/golang-manual-di"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/golang-manual-di/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/soulcodex/agentic/golang-manual-di"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/golang-manual-di.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.00097 | $0.03316 |
| Opus 5 | $0.00048 | $0.01658 |
| Sonnet 5 | $0.00019 | $0.00663 |
| Haiku 4.5 | $0.00010 | $0.00332 |
Grade A, and why
golang-manual-di 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 12d 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 — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manual Dependency Injection for Go Services
This skill walks through the 7-step process for wiring a Go service by hand — no code generation, no reflection containers. Each step maps to patterns observed in production cmd/di/ packages.
Naming Convention Taxonomy
Every function in the DI layer follows one of three tiers that communicate risk to the reader:
| Pattern | Intent | Risk |
|---|---|---|
Provide…() / provide…() |
Returns a value, no possible failure | None — safe to call anywhere |
MustProvide…() / mustProvide…() |
Builds infra that can panic on misconfiguration | Panics on bad config |
Must…() / must…() |
Starts a long-running service/process | Panics, process-level |
Rules:
- Provide tier — Use for infallible constructors. Functions that do no I/O and cannot fail. Example:
provideLogger(cfg LogConfig) zerolog.Logger. Never useMusthere. - MustProvide tier — Use for infrastructure builders that can panic (DB pools, cloud clients, OTEL init). The risk is confined to the init path — if it panics, the service never starts.
- Must tier — Use for entrypoints that spin up goroutines running servers or workers. The risk is process-level — if it panics, the process terminates.
Decision flowchart:
- Does the function return a value? → If NO → skip to question 2. If YES → Go to question 3.
- Does it perform side-effectful bootstrap that wires a global? (e.g. OTEL SDK init) → If YES → use
init…(the only valid use). If NO → error — every function must return a value or be a true bootstrap. - Does the function do I/O or have a failure path? → If NO → Use Provide tier. If YES → Can it panic instead of returning an error? → If YES → Use MustProvide tier (for infra) or Must tier (for entrypoints). If NO → Return
(T, error)instead.
Note on init…:
The init… prefix is reserved only for true one-shot side-effectful bootstrap that wires a global and does not return a usable value. Example: mustInitOTEL(ctx, cfg) wires the OTEL SDK as a global and returns nothing. Every other function that constructs and returns a dependency must use Provide… or MustProvide….
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 330 lines · 97 tokens per session scan A ffeaf637505c
golang-manual-di is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed 8d ago), licensed MIT. It adds 97 tokens to every session and 3,316 once invoked, about $0.0005 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-31.
Other skills, from other repositories
printing-press-amend
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally…
printing-press
Set up a new integration, connector, or CLI binding for any API. Wrap or generate a ship-ready Go CLI from an OpenAPI, HAR, or Postman spec via the lean research -> generate -> build -> shipcheck loop. Use when the user says build a CLI, wrap this API, set up a new integration, add a connector, integrate with a…
scaffold-project
Scaffold a new app, API, backend, fullstack project, mobile app, polyglot service, monorepo, or starter with Better Fullstack. Use when the user wants to create, start, bootstrap, initialize, or generate a project from a stack description. Prefer the bundled Better Fullstack MCP server: guidance, schema…
write-microflows
Microflow syntax reference in MDL — every activity type, control flow, expressions, and the mistakes that fail mxcli check. Use before writing any CREATE MICROFLOW, and when debugging a microflow syntax error.
json-structures-and-mappings
Create and manage JSON structures, import mappings and export mappings in MDL, plus the domain-model shapes they map onto. Use when turning a JSON payload into entities, mapping a REST or queue response, or exporting objects as JSON.
database-connections
Connect a Mendix app to an external database over JDBC with the External Database Connector, and define the queries microflows run against it. Use when the app must read or write Oracle, PostgreSQL, MySQL or SQL Server directly from a microflow.