Borrowing it
Nothing to install: this file belongs to frostney/GocciaScript. 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/frostney/GocciaScript/main/.agents/skills/implement/SKILL.mdgit clone --depth 1 https://github.com/frostney/GocciaScriptWrote 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/frostney/gocciascript/implement)<a href="https://agentmods.dev/skills/frostney/gocciascript/implement"><img src="https://agentmods.dev/badge/skills/frostney/gocciascript/implement/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/frostney/gocciascript/implement"><img src="https://agentmods.dev/badge/skills/frostney/gocciascript/implement.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.00045 | $0.01136 |
| Opus 5.5 | $0.00018 | $0.00454 |
| Sonnet 5.5 | $0.00009 | $0.00227 |
| Haiku 4.5 | $0.00005 | $0.00114 |
Grade A, and why
implement 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement
Develop the smallest complete change that satisfies the agreed requirements. Reuse settled scope, approach and authorization. A failed check, diagnosis or available fix does not end implementation. Only a material unresolved decision, new authority or an external blocker after safe alternatives are exhausted can stop dependent work; complete independent work before asking. If a skill requires a pause, link its loaded file as a Markdown link and quote the rule verbatim in a block quote; a paraphrase or a bare path does not let the user check the rule.
Establish the work
Infer the target from the request, conversation, handoff and repository; no issue/idea selector is required. Verify an identified issue's repository, requirements, comments, readiness and current state. A failed lookup does not make it an unfiled idea. For a described outcome, search for matching work and reuse its decisions. Otherwise establish a concise mini-spec with the outcome, scope, constraints and testable success measures; do not file an issue merely to implement it. Resolve conflicting or ambiguous targets before editing.
Read project instructions, relevant code, tests and durable decisions. Use the nearest Definitions of Ready and Done; if absent after a real search, use the workflow's checks and declared project commands and record the acceptance gap. Inspect the selected toolkit's overall capabilities before adding machinery. Run the named reproduction or inspect the artifact. If an issue is already fixed, verify its current behavior and regression coverage rather than duplicate it; add missing coverage when that is the remaining requirement.
Reuse a settled approach after checking it against current evidence. Research
primary sources when a decision depends on current external facts and reconcile
them with the installed version. For an unresolved material choice or requested
comparison, read references/approach-selection.md.
It owns comparison evidence and the registered grilling loop. Explicit
automatic mode skips that interview while preserving investigation and the
user's ownership of material product, architecture, security or scope choices.
If a search or source for required external evidence fails, reach the same
primary source another way, such as the installed package's documentation URL
or shipped declarations, and report that route. Stop the dependent work only
when no route works; continue independent investigation and any established
in-scope correction. A conclusively failed readiness threshold blocks dependent
work the same way.
What ships with it
1 file 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.
- yesterday Changed · +8 lines e575e76bbf4b
- 18d ago Changed bf7de8a9b4de
- 22d ago Changed · +3 lines 703da72dc427
- 26d ago Changed · +6 lines · +14 tokens per session 96458cb17682
- 29d ago First seen · 85 lines · 31 tokens per session scan A 6f8f9960905d
implement is a skill published in the GitHub repository frostney/GocciaScript (20 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 1,136 once invoked, about $0.0002 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-09-26.
Other skills, from other repositories
stacking-prs
Create and manage GitHub native Stacked PRs in this repo with the gh stack CLI. Use when asked to stack PRs, split a large change into a stack, add a layer to a stack, restack or rebase a stack, adopt existing branches or PRs into a stack, check out someone else's stack, or land a stack. Covers creating and submitting…
herdr-kit-workflows
Set up and operate Herdr Kit safely: install and configure the plugin and Mastra Code integration, manage Review and Work repository scope, open primary repository workspaces, synchronize managers, materialize or dematerialize managed worktrees, and update Herdr Kit settings or shortcuts.
herdr-manager-query
Query the authoritative global Herdr Review and Work Manager inventory, recommend actionable PR work, and explicitly materialize confirmed remote-only Review Manager records through the plugin's stable public CLI.
claim-issue
Atomically claim an issue for a developer (human or agent) via the cross-developer lock ref, so two devs never pick up the same task. Syncs with origin first, refuses if already claimed or already done on main, and pushes the claim immediately without touching main or triggering CI.
tech-lead-loop
The tech lead's standing loop for keeping development unblocked across a sprint. Defines phase-by-phase protocol enforcement, merge-queue monitoring, and escalation triggers. Invoke at session start, again after every significant state change, and whenever devs look idle.
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.…