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 LichAmnesia/lich-skills --skill go-no-gogit clone --depth 1 https://github.com/LichAmnesia/lich-skillsWrote 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/lichamnesia/lich-skills/go-no-go)<a href="https://agentmods.dev/skills/lichamnesia/lich-skills/go-no-go"><img src="https://agentmods.dev/badge/skills/lichamnesia/lich-skills/go-no-go/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/lichamnesia/lich-skills/go-no-go"><img src="https://agentmods.dev/badge/skills/lichamnesia/lich-skills/go-no-go.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 67 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00169 | $0.03961 |
| Opus 5 | $0.00084 | $0.01980 |
| Sonnet 5 | $0.00034 | $0.00792 |
| Haiku 4.5 | $0.00017 | $0.00396 |
Grade A, and why
go-no-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 10d 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 — 399 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go / No-Go — Stage 0
NO-GO is the default. GO requires evidence.
Most AI coding skills help you build. This one helps you not build.
Half the cost of solo work is starting the wrong thing. Once a repo exists, sunk cost and identity-protection make it hard to quit. So you grind 3–6 months before admitting the start itself was wrong.
go-no-go is the gate before any /spec, /plan, /build. It runs five
framework checks (configurable), a memory check against your own past
attempts, and a 24-hour cooldown if your enthusiasm is too high. The output
is a public commitment doc with pre-mortemed kill criteria. If anything
fails, the default is NO-GO.
It is a deliberately stronger instrument than a generic intent-extraction interview: it stores memory, fails by default, requires structural overrides, and produces a dated artifact you publish.
When to Use
Run /go-no-go when:
- You catch yourself thinking "I should build X" / "I want to start Y" / "I should take on Z client"
- Before opening any new git repo
- Before signing any client contract or partnership
- Before any commitment with attention budget > 14 days
- Before invoking
/spec,/plan, or/buildon a new thing - When you feel sudden enthusiasm — especially then
When NOT to Use
- Continuing existing committed projects (use
/specdirectly) - Tactical pivots within an already-confirmed project
- Pure information requests ("how does X work?")
- Daily journaling or routine work
- Reactive content (writing about a news event, not a project commitment)
- One-off tasks under ~4 hours
How It Differs From Other Pre-Build Skills
| Plain intent interview | go-no-go |
|
|---|---|---|
| Default outcome | Continue | NO-GO |
| Memory of past attempts | None | Mandatory pre-flight search |
| Framework checks | Generic restate | 5 fail-by-default gates |
| Time gate | None | 24h pattern-interrupt if enthusiasm-high |
| Output | Confirmed restate | Public commitment doc with kill criteria |
| Override semantics | "Yes/no" | Structured override with named reason |
| Lifecycle | One session | D14/D30/D60/D90 review schedule |
| Composability | Standalone | Stage 0 of any SDLC (pairs with spec-driven-dev) |
What ships with it
7 files 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.
- 10d ago First seen · 399 lines · 169 tokens per session scan A 230c21a4775a
go-no-go is a skill published in the GitHub repository LichAmnesia/lich-skills (233 stars, last pushed 3mo ago), licensed MIT. It adds 169 tokens to every session and 3,961 once invoked, about $0.0008 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-30.
Other skills, from other repositories
gws-gmail-send
Skill "gws-gmail-send" from googleworkspace/cli, covering gmail +send, usage, flags, examples and tips.
gws-shared
The gws binary must be on $PATH. See the project README for install options.
gws-sheets
Google Sheets: Read and write spreadsheets.
gws-gmail
Gmail: Send, read, and manage email.
gws-modelarmor-create-template
Google Model Armor: Create a new Model Armor template.
gws-modelarmor
Google Model Armor: Filter user-generated content for safety.