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 agentmods add commands/armanzeroeight/fastagent-plugins/check-gogit clone --depth 1 https://github.com/armanzeroeight/fastagent-pluginsWrote 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/commands/armanzeroeight/fastagent-plugins/check-go)<a href="https://agentmods.dev/commands/armanzeroeight/fastagent-plugins/check-go"><img src="https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/check-go.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.00603 |
| Opus 5 | $0.00008 | $0.00302 |
| Sonnet 5 | $0.00003 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
check-go 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 yesterday.
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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Go
Run comprehensive Go code quality checks.
Context
- Go version: !
go version - Current directory: !
pwd - Go files: !
find . -name "*.go" -not -path "*/vendor/*" | head -10
Your Task
Run Go code quality checks and provide actionable feedback.
Arguments
$1: Optional--fixflag to automatically fix issues
Steps
-
Check Go installation
- Verify go command is available
- Check Go version
-
Run gofmt
- Check code formatting
- If --fix: Apply formatting
- Report unformatted files
-
Run go vet
- Check for suspicious constructs
- Report issues found
- Provide fix suggestions
-
Run staticcheck (if available)
- Advanced static analysis
- Check for bugs and inefficiencies
- Report findings
-
Run go test
- Execute all tests
- Report test results
- Show coverage if available
-
Check for race conditions
- Run tests with -race flag
- Report any race conditions
-
Provide summary
- List all issues found
- Categorize by severity
- Suggest fixes
- Show overall status
Output Format
# Go Code Quality Report
## Formatting
- Status: [PASS/FAIL]
- Unformatted files: [count]
- [List of files if any]
## Go Vet
- Status: [PASS/FAIL]
- Issues found: [count]
- [List of issues with file:line]
## Static Analysis
- Status: [PASS/FAIL/SKIPPED]
- Issues found: [count]
- [List of issues]
## Tests
- Status: [PASS/FAIL]
- Tests run: [count]
- Passed: [count]
- Failed: [count]
- Coverage: [percentage]
## Race Detection
- Status: [PASS/FAIL/SKIPPED]
- Races found: [count]
## Summary
- Overall: [PASS/FAIL]
- Total issues: [count]
- Action required: [yes/no]
## Recommendations
1. [Fix suggestion 1]
2. [Fix suggestion 2]
...
Examples
Check code quality:
/check-go
Check and auto-fix:
/check-go --fix
Expected output:
- Formatting status
- Vet results
- Static analysis findings
- Test results
- Race detection results
- Actionable recommendations
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.
- yesterday First seen · 122 lines · 16 tokens per session scan A bf5f5b4e9778
check-go is a command published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 603 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
MIGRATE_DESIGN
Design doc for the migration tool PR. Author: Sol ([email protected]). Co-authored-by: wakesync.
triage-pr
Triage a PR — classify, optionally fix, optionally enable auto-merge.
tech-debt
Run bun run check:fix and then bunx knip and identify unused files and functions to refactor the project and simplify. Look at the deprecated features and confirm with the user to delete them. Look at the dependencies and remove the ones that are not needed based on knip results.
OPSX: Verify
Verify implementation matches change artifacts before archiving.
OPSX: Archive
Archive a completed change in the experimental workflow.
OPSX: Sync
Sync delta specs from a change to main specs.