Borrowing it
Nothing to install: this file belongs to usk6666/yorishiro-proxy. 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/usk6666/yorishiro-proxy/main/.claude/skills/implement/SKILL.mdgit clone --depth 1 https://github.com/usk6666/yorishiro-proxyWrote 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/usk6666/yorishiro-proxy/implement)<a href="https://agentmods.dev/skills/usk6666/yorishiro-proxy/implement"><img src="https://agentmods.dev/badge/skills/usk6666/yorishiro-proxy/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/usk6666/yorishiro-proxy/implement"><img src="https://agentmods.dev/badge/skills/usk6666/yorishiro-proxy/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.00022 | $0.01349 |
| Opus 5.5 | $0.00009 | $0.00540 |
| Sonnet 5.5 | $0.00004 | $0.00270 |
| Haiku 4.5 | $0.00002 | $0.00135 |
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 13d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/implement
An end-to-end workflow skill for implementing a Linear Issue through to PR creation.
Arguments
/implement <Issue ID>— Implement the specified Issue (e.g.,/implement USK-12)
Steps
- Load Issue: Fetch Issue details with
mcp__linear-server__get_issue - Update Issue status: Update status to "In Progress"
- Create branch: Generate an appropriate branch name from the Issue
- feat:
feat/<id>-<short-desc> - fix:
fix/<id>-<short-desc> - other:
chore/<id>-<short-desc>
- feat:
- Design review (mandatory for any Issue that introduces a new public type, modifies an interface, or touches more than one package; skip for docstring-only / test-only / single-call-site fixes — note the skip reason in the user-facing plan): launch the design-reviewer agent. See "Design Review Invocation" below.
- Present plan to user: Issue summary, file actions (new / modified / untouched), key resolved decisions from the design review, the Test Plan (the failing tests that will be written first), deferred items, unresolved questions. Get user confirmation before implementing. For trivial Issues that skipped Step 4, present a one-paragraph plan that still names the failing test(s) to write first, or the TDD exemption that applies.
- Red — write failing tests first: Follow "TDD Workflow" Phase 1 in
.claude/agents/implementer.md(it is the single source for the rules and exemptions). Write the tests plus compile-only scaffolding, run them withmake test-pkg PKG=<pkg> RUN=<regexp>, confirm each fails on its assertion (not a compile error orno tests to run), and commit them alone astest(<scope>): add failing tests for <Issue ID>. Keep the--- FAIL:lines for the PR body. - Green, then refactor: Implement until the Phase 1 tests pass, without weakening any Phase 1 assertion (implementer.md Phase 2), then refactor.
- Verify:
- Auto-format with
gofmt -w . make lint(gofmt check + golangci-lint: govet / staticcheck / unused / ineffassign / gocyclo)make buildmake test
- Auto-format with
- Commit: Commit in Conventional Commits format, as a separate commit after the Step 6 red commit (do not amend or squash them together)
- Include
Refs: <Issue ID>in the commit message footer
- Include
- Push: Push to remote with
git push -u origin <branch-name> - Create PR:
- Review changes with
git diff main...HEAD - PR title in Conventional Commits format (e.g.,
feat(protocol): add HTTP handler) - PR body follows the template below
- Create PR with
gh pr create
- Review changes with
- Update Issue status: Update status to "In Review"
- Report results: Display implementation summary + PR URL
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.
- 13d ago Changed · +8 lines 61268028551b
- 1mo ago Changed 491ff55da2db
- 1mo ago First seen · 92 lines · 22 tokens per session scan A 65d3fd7be45a
implement is a skill published in the GitHub repository usk6666/yorishiro-proxy (19 stars, last pushed yesterday), licensed Apache-2.0. It adds 22 tokens to every session and 1,349 once invoked, about $0.0001 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-30.
Other skills, from other repositories
papi-build
Invoke when executing a build via buildexecute. Covers branching, gestalt pre-build check, and post-build audit.
papi-auto
Continue an approved PAPI cycle through implementation, verification and review using bounded autonomy. Resume durable work without rebuilding it; propose new scope before persisting it.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
gait-session-tracking
GAIT session lifecycle management - branch creation, turn recording, audit logging for every NetClaw operation. Use when starting a new NetClaw session, recording a health check or config change, pinning a pre-change baseline, or viewing the audit trail for a troubleshooting session.
deliver-spec
Use when explicitly asked to deliver an approved GitHub or local spec through a reviewed pull request, or when a Project controller delegates one claimed implementation ticket.