What is implement-ticket?

A workflow for completing one software ticket, checking the result, saving repository changes, and closing the ticket when the work is proven complete.

Use it for code changes as well as documentation, configuration, migrations, workflow updates, or tracker-only work.

It keeps implementation, verification, and ticket status tied to the actual requirements and changed parts of the project.

How sponge-b0b/Polaris configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to sponge-b0b/Polaris. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/sponge-b0b/Polaris/main/.agents/skills/implement-ticket/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/sponge-b0b/Polaris

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sponge-b0b/polaris/implement-ticket/github.svg)](https://agentmods.dev/skills/sponge-b0b/polaris/implement-ticket)

Your own site

<a href="https://agentmods.dev/skills/sponge-b0b/polaris/implement-ticket"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/implement-ticket/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sponge-b0b/polaris/implement-ticket"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/implement-ticket.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,571 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 2 findings, up to high

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 →

high Prompt Injection · line 74
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.

Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
medium Excessive Agency · line 611
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00029	$0.02571
Opus 5.5	$0.00012	$0.01028
Sonnet 5.5	$0.00006	$0.00514
Haiku 4.5	$0.00003	$0.00257

Measured today against content hash 8d25074daf0d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

implement-ticket 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 today.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/attention_gate_impl.py, scripts/attention_gate.py, tests/test_attention_gate.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.agents/skills/implement-ticket/SKILL.md · 219 lines

How it starts

The opening of the file, as written. The whole thing — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Implement Ticket

Authoritative procedure composition

Before executing this skill, read all of these files in full:

.agents/skills/implement-ticket/ROUTING_CONTROL_PLANE.md
.agents/skills/to-tickets/TICKET_RESLICE_RECOVERY.md
.agents/skills/WORKFLOW_INVOCATION_JOURNAL.md
.agents/skills/implement-ticket/WORKFLOW_INVOCATION_JOURNAL.md

ROUTING_CONTROL_PLANE.md preserves the previously authoritative $implement-ticket entrypoint and recursively composes PROCEDURE.md, EXECUTION_ANCHOR.md, and CONTROL_PLANE.md, including the protected workflow/control-plane boundary, durable routing defects, deterministic ticket contract, Attention, closure, and shared Human Handoff rules. TICKET_RESLICE_RECOVERY.md is the canonical durable contract for every ticket-reslice-recovery:v1 record and overrides the shorter recovery summary retained in PROCEDURE.md. WORKFLOW_INVOCATION_JOURNAL.md at the skills root owns the shared WIJ storage/schema/non-authority contract; this skill's WIJ document owns only $implement-ticket integration and resume classification. On any other conflict, this file wins. Failure to load either retained execution/recovery authority file is a Hard Blocker.

WIJ is a best-effort execution optimization, never a lifecycle prerequisite. Journal failure, loss, corruption, ambiguity, or incompatibility must degrade to the ordinary current $implement-ticket reconstruction and must not create a new blocker or termination state. Only an explicit resume $implement-ticket - <Title> (<URL>) invocation may consume an old journal; an ordinary invocation starts fresh.

All retained requirements remain mandatory unless explicitly overridden here.

Execution-anchor invariant

Retain the accepted distinction between the immutable historical Ticket baseline and the current attempt's Execution Anchor. Do not require the current shared branch to equal that historical SHA. Before a fresh attempt, fetch the actual remote ticket branch and, only while clean, fast-forward only when the local branch is strictly behind and is an ancestor. The retained Execution Anchor and Attention-gate rules remain mandatory.

Read the full file on GitHub · 219 lines

Files

What ships with it

10 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.

Changes

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.

today Changed · +3 lines 8d25074daf0d
yesterday Changed · +49 lines 82dd215c1bc5
4d ago Changed · +10 lines 1e6e16eacb95
5d ago Changed · -93 lines 5ffc09926722
6d ago Changed · -232 lines 0583f9d55e20
7d ago Changed · +6 lines d6912a495d10
8d ago Changed · -1,185 lines ff10ff3ee147
13d ago Changed · +24 lines 838ce6290e85
14d ago Changed · +21 lines 4ec638856407
16d ago First seen · 1,616 lines · 29 tokens per session scan A 8b94a3fe1952

Subscribe to this mod's changes

implement-ticket is a skill published in the GitHub repository sponge-b0b/Polaris (4 stars, last pushed today), licensed Apache-2.0. It adds 29 tokens to every session and 2,571 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-31.

Project management

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

handle-linkedin-connection-request-signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…

swan-gtm/gtm-skills · 160 tokens

Polaris: Skill for Claude Code