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/gopherguides/gopher-aiWrote 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/gopherguides/gopher-ai/go-workflow)<a href="https://agentmods.dev/plugins/gopherguides/gopher-ai/go-workflow"><img src="https://agentmods.dev/badge/plugins/gopherguides/gopher-ai/go-workflow/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/gopherguides/gopher-ai/go-workflow"><img src="https://agentmods.dev/badge/plugins/gopherguides/gopher-ai/go-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
go-workflow 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.
What it actually says
{
"name": "go-workflow",
"description": "Issue-to-PR workflow automation with git worktree management",
"version": "1.11.3",
"author": {
"name": "Gopher Guides",
"email": "[email protected]"
},
"homepage": "https://gopherguides.com",
"repository": "https://github.com/gopherguides/gopher-ai",
"license": "MIT",
"keywords": [
"workflow",
"github",
"issues",
"pr",
"worktree"
]
}
What it installs
The manifest is a name and a version. 11 skills, 3 commands, 4 agents, 4 hooks travel with it, and installing the plugin installs all of them — 745 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill tmux-start A 70 tokens
- Skill create-pr A 44 tokens
- Skill commit A 60 tokens
- Skill cancel-loop A 29 tokens
- Skill complete-issue A 53 tokens
- Skill e2e-verify A 69 tokens
- Skill review-deep A 72 tokens
- Skill ship A 51 tokens
- Skill start-issue A 64 tokens
- Skill address-review A 62 tokens
- Skill worktree A 43 tokens
- Command remove-worktree A 9 tokens
- Command create-worktree A 14 tokens
- Command prune-worktree A 8 tokens
- Agent implementer-prompt A 20 tokens
- Agent quality-review-prompt A 27 tokens
- Agent spec-review-prompt A 22 tokens
- Agent explore-prompt A 28 tokens
- Hook PreToolUse A not measured
- Hook SessionStart A not measured
- Hook PostToolUse A not measured
- Hook Stop A not measured
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 Changed e0bc8c3559f5
- 1mo ago Changed e2fa3a86bf77
- 1mo ago Changed 46442b5b494f
- 1mo ago Changed a2cbcc058ecd
- 1mo ago Changed 95a536fe9c69
- 1mo ago First seen · 20 lines scan A 1383993719af
go-workflow is a plugin published in the GitHub repository gopherguides/gopher-ai (21 stars, last pushed yesterday), 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
fuse-rules
Global rules for all Claude Code sessions: APEX workflow, SOLID/DRY enforcement, project detection, agent delegation, frontend/git standards.
lanes-bridges
Bridge Lanes with GitHub and Linear: import issues, batch-spawn a session per ticket, and post results back upstream. Split out of lanes-desktop in 0.7.0.
dev
Ralph Loop development lifecycle: ticket assignment through merge-ready PR. Includes start, code, pr, poll, ci, backport, work, grill-with-docs, to-prd, to-issues, handoff, and qe.
workbench
Ticket-to-PR development workflow: triage, plan with verified citations, implement inside the plan, review, commit, PR. Pluggable issue trackers (Jira, Azure DevOps, GitHub Issues) or a backlog in the repo, so it works with no tracker at all.
gh-cli
GitHub CLI integration with focused skills for pull requests, stacked pull requests, issues, GitHub Actions, and viewing GitHub file URLs.
tgc-skills
A shipping pipeline for Claude Code: orchestrate a locked plan with fresh-context agents, polish the diff, ship it to a reviewed PR, run an agent review-fix loop until clean, and clean up after merge.