Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add sgaunet/claude-plugins/plugin install go-specialistWrote 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/sgaunet/claude-plugins/gen-forgejo-dir)<a href="https://agentmods.dev/skills/sgaunet/claude-plugins/gen-forgejo-dir"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/gen-forgejo-dir/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/sgaunet/claude-plugins/gen-forgejo-dir"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/gen-forgejo-dir.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00029 | $0.07478 |
| Opus 5.5 | $0.00012 | $0.02991 |
| Sonnet 5.5 | $0.00006 | $0.01496 |
| Haiku 4.5 | $0.00003 | $0.00748 |
Grade A, and why
gen-forgejo-dir 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 22d 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 — 669 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate .forgejo Directory
Instantly create a complete .forgejo/workflows directory structure for Go projects with production-ready, mise-based Forgejo Actions workflows (linting, coverage, snapshot builds, releases).
Forgejo Actions reuses GitHub-Actions-compatible workflow syntax, so the workflow content is identical to what /gen-github-dir produces. The key differences are the directory location (.forgejo/workflows/ instead of .github/workflows/), the runs-on runner label, and the action/registry source assumptions described below.
Like the GitHub variant, the workflows install tooling via jdx/mise-action@v3 and run task …, so CI uses the exact tool versions pinned in mise.toml (created at the repo root if missing). This also shrinks the set of GitHub actions that must be mirrored on your instance to just actions/checkout and jdx/mise-action.
Why This Skill Exists
Problem: Setting up CI/CD for Go projects on a Forgejo instance requires manually creating multiple workflow files, understanding that Forgejo Actions mirrors GitHub Actions syntax but lives under a different directory, and wiring up runner labels - a 30-60 minute process.
Solution: One-command generation that:
- Creates a complete
.forgejo/workflowsdirectory structure - Includes comprehensive workflows: linting, coverage, snapshot builds, releases
- Targets a Forgejo Actions runner label (not
ubuntu-latest) - Preserves all customization comments for user control
Forgejo Actions Assumptions
This skill makes the following assumptions about your Forgejo instance. Review them before running:
- Runner label — Workflows are generated with
runs-on: docker(a common default label for the official Forgejo Actions runner). You must have at least one registered Forgejo Actions runner that advertises this label. Manage runners with the Forgejo CLI:
If your runner uses a different label (e.g.fgj actions runner list # List registered runners and their labels fgj actions runner register # Register a new runnerself-hosted,ubuntu-latest, or a custom label), editruns-on:in the generated files or re-run after adjusting your runner registration. Without a matching registered runner, workflows will queue forever.
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.
- 22d ago First seen · 669 lines · 29 tokens per session scan A 52744e4652f3
gen-forgejo-dir is a skill published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 8d ago), licensed MIT. It adds 29 tokens to every session and 7,478 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-09-25.
Other skills, from other repositories
implementing-go
Implements concise, streamlined Go code matching exact architect specifications. Use when writing Go code, creating packages, or when the user asks to implement features in Go.
reviewing-go
Provides concise, focused Go code reviews matching exact task complexity requirements. Use when reviewing Go code quality, concurrency safety, or when the user asks for code review.
golang-continuous-integration
GitHub Actions CI/CD pipeline configuration for Golang projects — workflow files for test, lint, SAST, coverage and vulnerability-scan jobs, Dependabot and Renovate config files, GoReleaser release pipelines, Docker build/push, repository security settings, and AI-driven PR review. Use when setting up or improving Go…
tree-sitter-language-pack-managing-parsers
Use when the user needs to manage the tree-sitter parser cache — prefetch parsers for offline or CI runs, list what is downloaded, inspect a language, find the cache directory, or clean it. Covers ts-pack download, list, info, cache-dir, clean, and init.
dotnet-analyzers
Run dotnet format to fix code style and analyzer diagnostics (IDE0005, CA, SA). Use when fixing unnecessary usings, code style violations, analyzer warnings, or verifying format compliance.
dotnet-dependency
This skill should be used when investigating .NET project dependencies, understanding why packages are included, listing references, or auditing for outdated/vulnerable packages.