Borrowing it
Nothing to install: this file belongs to nbiish/agentsstandard-dot-com. 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/nbiish/agentsstandard-dot-com/main/.agents/skills/gstack-coder/SKILL.mdgit clone --depth 1 https://github.com/nbiish/agentsstandard-dot-comWrote 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/nbiish/agentsstandard-dot-com/gstack-coder)<a href="https://agentmods.dev/skills/nbiish/agentsstandard-dot-com/gstack-coder"><img src="https://agentmods.dev/badge/skills/nbiish/agentsstandard-dot-com/gstack-coder/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/nbiish/agentsstandard-dot-com/gstack-coder"><img src="https://agentmods.dev/badge/skills/nbiish/agentsstandard-dot-com/gstack-coder.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.00102 | $0.02315 |
| Opus 5.5 | $0.00041 | $0.00926 |
| Sonnet 5.5 | $0.00020 | $0.00463 |
| Haiku 4.5 | $0.00010 | $0.00231 |
Grade A, and why
gstack-coder 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.
How it starts
The opening of the file, as written. The whole thing — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GStack Coder — Multi-Tool Coding Orchestration
This skill combines gstack (Claude Code skill pack) with pi and mini to form a complete multi-tool coding workflow. Each tool has unique strengths and subscription quotas — this skill ensures all are utilized.
PRD Anchor: Always read llms.txt in the repository root first. It is the authoritative Product Requirements Document for this repo — it defines architecture, security policy (PQC mandates, secrets management), workflow rules (git worktrees, commit conventions), and the provider/MCP infrastructure. If llms.txt and any other doc conflict, llms.txt wins. Never skip reading it.
1. GStack Installation & Setup
gstack is a collection of Claude Code skills by garrytan. Install once:
git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack && cd ~/.claude/skills/gstack && ./setup
After installation, gstack provides these slash commands inside Claude Code:
| Command | Purpose |
|---|---|
/cso |
Security audit — full codebase security review |
/review |
Code review — detailed PR/code review |
/qa https://... |
QA test a URL — test a deployed endpoint |
/autoplan |
Auto-plan — generate implementation plan for a feature |
/ship |
Ship — build, test, and deploy pipeline |
/office-hours |
Office hours — architect/planning discussion before building |
2. Multi-Tool Coding Workflow
Tool Inventory
| Tool | CLI | Config Location | Best For |
|---|---|---|---|
| Claude Code (gstack) | claude |
~/.claude/ |
Security audits, code review, planning, shipping |
| pi | pi (wrapper) |
~/.pi/agent/ |
Fast non-interactive coding, extensions, themes, MCP servers |
| mini | mini (wrapper) |
~/.config/mini-swe-agent/.env |
Lightweight SWE agent, bash-based tasks |
Provider Hot-Swap (use all subscriptions)
The ainish-coder framework supports hot-swapping provider configs via CLI wrappers. Each tool can be pointed at different API providers to maximize quota usage:
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 First seen · 242 lines · 102 tokens per session scan A a675a322e434
gstack-coder is a skill published in the GitHub repository nbiish/agentsstandard-dot-com (2 stars, last pushed 5mo ago), licensed MIT. It adds 102 tokens to every session and 2,315 once invoked, about $0.0004 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-31.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…