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 skills/frostney/gocciascript/implement-ideanpx skills add frostney/GocciaScript --skill implement-ideagit clone --depth 1 https://github.com/frostney/GocciaScriptWhat 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.00052 | $0.01243 |
| Opus 5 | $0.00026 | $0.00622 |
| Sonnet 5 | $0.00010 | $0.00249 |
| Haiku 4.5 | $0.00005 | $0.00124 |
Grade A, and why
implement-idea 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 2d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement idea
Turn the idea into a confirmed mini-spec, then deliver it end to end in the current repository.
Gates
- Start with a provisional mini-spec of at most 400 characters, including spaces. Confirm the final mini-spec covering the user-visible outcome, scope/non-goals, and verifiable success criteria only after the artifact-assisted grill.
- Read project instructions, vision, contribution guidance, Definition of Ready, Definition of Done, relevant domain skills, real project commands, affected code paths, tests, and related work before deciding.
- Always perform and record web search for current evidence before presenting options. Prefer official and primary sources, reconcile them with the versions in the checkout, and treat remembered links only as search leads. Stop if the search cannot produce current evidence relevant to the decision.
- When
grill-with-docsorgrill-meis registered, run its actual user-question loop before presenting options. Prefergrill-with-docs; if neither exists, note that once and continue. - Before proposing an option, assemble one neutral evidence packet from the repository, reproduction, project contracts, current web research, and shared current-state artifacts. Derive every option from this same packet.
- Define one comparison rubric from the confirmed outcome, constraints, and
success criteria before scoring. Give every viable option equivalent
decision-relevant validation:
- for UI/UX differences, show each materially different experience;
- for architecture or workflow differences, show each relevant flow;
- for interaction-heavy or technical claims, use comparable short-lived prototypes or measurements when static evidence cannot decide them. Equivalent checks do not require equal implementation effort. Label observed facts, proposed behavior, and prototype-only shortcuts.
- If an option reveals an evidence gap, run the same relevant check for every affected option. When that is impossible, disclose the unequal evidence and reduce confidence before comparison.
- Keep prototypes local and disposable, retain only reviewable captures and
findings, and remove them when the grill concludes. Do not deploy or publish
them. Preserve or promote a prototype only with explicit user approval; keep
approved prototype material outside the selected worktree until its
git-workflowsynchronization gate passes. - Compare two to four genuinely distinct viable options against the declared rubric, then recommend one and wait for the user's choice unless automatic mode applies. Include a compact evidence digest with the most relevant source links, checked project versions, scores, and remaining uncertainty.
- For any code or test change, complete the project gate, one bounded
/code-review fix-all, and/create-pr.
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.
- 2d ago First seen · 108 lines · 52 tokens per session scan A 25166ecbdae0
implement-idea is a skill published in the GitHub repository frostney/GocciaScript (20 stars, last pushed 6d ago), licensed MIT. It adds 52 tokens to every session and 1,243 once invoked, about $0.0003 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
git-step-commit
Analyze Git changes, split them into coherent commits, infer message language and format, optionally close supplied GitHub issues, and execute safely. Manage persistent global or repository preferences for review versus direct submission and automatic or specified commit-message language through native Git config.…
git-workflow
Applies the user's git defaults: branch from the remote default, merge rather than rebase, never amend or force-push, and squash-merge pull requests. Use when branching, syncing, committing, pushing, or merging in the user's repos.
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
submit-pr-from-current-changes
Create a branch, commit existing local changes, push them, and open a pull request. Use when submitting current work as a PR.
commit
Commit message formatting and guidelines.
commit
Create a git commit with optional automatic Linear issue linking. Use when the user asks to commit.