agentmods.dev

ticket-closer

ticket-closer is an agent for coding agents from Hulupeep/Specflow. It costs 0 tokens per session (1,734 once invoked), scanned A, original, MIT.

An agent that manages the life cycle of GitHub issues, which are records of bugs, tasks, or requested changes.

In plain words
What is it for?
It is for updating tickets after code changes, checking whether issues are finished, and handling special verification for user-interface work.
Why use it?
It connects implementation work to issues, adds progress comments, and closes issues only after required checks are complete.

Agent

not rated 25 1mo ago A scan 0 tokens original MIT
View the source file Hulupeep/Specflow
Install

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.

agentmods
npx agentmods add agents/hulupeep/specflow/ticket-closer
Clone the repo
git clone --depth 1 https://github.com/Hulupeep/Specflow

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.

agentmods badge for ticket-closer

README.md
[![agentmods](https://agentmods.dev/badge/agents/hulupeep/specflow/ticket-closer.svg)](https://agentmods.dev/agents/hulupeep/specflow/ticket-closer)
Your own site
<a href="https://agentmods.dev/agents/hulupeep/specflow/ticket-closer"><img src="https://agentmods.dev/badge/agents/hulupeep/specflow/ticket-closer.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,734 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01734
Opus 5 $0.00000 $0.00867
Sonnet 5 $0.00000 $0.00347
Haiku 4.5 $0.00000 $0.00173

Measured 5d ago against content hash bb7b203cf4bb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ticket-closer 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 5d 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.

agents/ticket-closer.md · 178 lines

How it starts

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

Agent: ticket-closer

Role

You are a GitHub issue lifecycle manager for your project. You map implementation work to GitHub issues, add implementation comments, and close completed issues.

haiku — Mechanical task: posts implementation comments and closes validated issues

Trigger Conditions

  • User says "update tickets", "close issues", "update github issues"
  • After implementation subagents complete their work
  • After a batch of commits has been made

Inputs

  • Git commit range (e.g., "since 3cbe334") or branch name
  • List of issue numbers to check
  • OR: "all open issues" to scan everything

Process

Step 0: Verify Journey Gate (MANDATORY -- runs before all other steps)

  1. Determine if issue is UI-facing. Check for ANY of:

    • Label: Frontend Interface or UI
    • Body contains TSi=Y or Tid=Y
    • Body contains data-testid
    • Body references any J-* journey ID

  2. If UI-facing: a. Search for a Tier 1 pass certificate in:

    • Issue comments (posted by journey-gate)
    • Current agent session output b. Certificate must contain:
    • JOURNEY GATE TIER 1: PASS
    • Issue: #<this issue number>
    • Commit: <SHA> where SHA matches git rev-parse HEAD c. If certificate is MISSING:
    Cannot close #<N>: No Tier 1 journey gate pass certificate found.
Run: "run journey gate tier 1 for issue #<N>"

    STOP. Do not proceed to Step 1. d. If certificate commit SHA does NOT match current HEAD:

    Cannot close #<N>: Tier 1 certificate is stale.
Certificate commit: <cert SHA>
Current HEAD: <current SHA>
Re-run: "run journey gate tier 1 for issue #<N>"

    STOP. Do not proceed to Step 1. e. If certificate is valid and current: proceed to Step 1.

  3. If NOT UI-facing: proceed to Step 1.

Step 1: Gather Implementation Evidence

  1. Run git log --oneline <range> to get commits
  2. Run git diff <range> --stat to get changed files
  3. Read each changed file to understand what was implemented
  4. Map files to features:
    • supabase/migrations/*.sql → database changes
    • supabase/functions/*/index.ts → Edge Functions
    • src/features/*/components/*.tsx → UI components
    • src/features/*/hooks/*.ts → data hooks
    • src/adapters/repositories/*.ts → data access
    • tests/e2e/*.spec.ts → test coverage

Read the full file on GitHub · 178 lines

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.

  1. 5d ago First seen · 178 lines · 0 tokens per session scan A bb7b203cf4bb

Subscribe to this mod's changes

ticket-closer is an agent published in the GitHub repository Hulupeep/Specflow (25 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,734 tokens. 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.

AI SafetyGit and workflowProject managementarchitecturecode-qualitycontractsdeveloper-tools
Related

Other agents, from other repositories

architect

Code architecture analyst, optimization planner, and feature architecture designer. Reviews code from a design perspective, identifies architectural improvements, creates prioritized optimization plans, performs final quality assessments, and designs comprehensive implementation blueprints for new features.

zircote-plugins/refactor · 45 tokens

code-reviewer

Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions. Merges security review capabilities including OWASP validation, secrets scanning, and regression detection. Uses confidence-based filtering for quality issues and severity classification for…

zircote-plugins/refactor · 65 tokens

api-architect

Use this agent PROACTIVELY when designing API architectures, defining contracts, planning integration patterns, making decisions about REST vs GraphQL, establishing authentication strategies, designing rate limiting systems, planning API versioning approaches, or creating OpenAPI specifications. Invoke for any API…

lando-labs/cami · 66 tokens

refactor-code

Code implementation specialist for refactoring workflows. Implements architectural optimizations focusing on clean code principles, fixes test failures, and ensures all changes preserve existing functionality without introducing bugs.

zircote-plugins/refactor · 37 tokens

feature-code

Implementation specialist for new feature development. Reads architecture blueprints and codebase context from the blackboard, then creates new code following established patterns and conventions. Designed for feature-dev workflows.

zircote-plugins/refactor · 39 tokens

refactor-test

Test coverage analyzer and test case generator for refactoring workflows. Analyzes code coverage, adds missing test cases to meet production requirements, runs tests, and ensures all tests pass before proceeding with refactoring.

zircote-plugins/refactor · 45 tokens