agentmods.dev

file

A command for creating GitHub Issues from approved gaps in the latest gap-analysis file. GitHub Issues are tracked work items for bugs, feature requests, or other changes.

In plain words
What is it for?
Use it to review gaps, adjust their scores, and create one issue or multiple issues with titles, descriptions, and labels. It requires the GitHub CLI to be authenticated and a recent .pm/gaps/*.md analysis file.
Why use it?
It removes repetitive issue creation and checks for similar existing issues first. It can also guide a review where each gap is marked FILE, WAIT, or SKIP before filing.

Command

483 1mo ago A scan 8 tokens original MIT
View the source file ooiyeefei/ccc
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 commands/ooiyeefei/ccc/file
Clone the repo
git clone --depth 1 https://github.com/ooiyeefei/ccc
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 487 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.00008 $0.00487
Opus 5 $0.00004 $0.00244
Sonnet 5 $0.00002 $0.00097
Haiku 4.5 $0.00001 $0.00049

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

Security

Grade A, and why

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

plugins/product-management/commands/file.md · 76 lines

What it actually says

Feature Filing

Create GitHub Issues for gaps marked "FILE" in gap analysis.

Prerequisites

  1. Check GitHub CLI availability:

    gh auth status

    If not authenticated: "Run gh auth login first."

  2. Check gap analysis exists:

    • Read latest .pm/gaps/*.md file
    • If missing: "Run /pm:gaps first."

Process

Without Arguments - Review Mode

Walk through each gap from latest analysis:

  1. Show gap with score and evidence
  2. Ask: "FILE / WAIT / SKIP?"
  3. Allow score adjustments
  4. Save decisions to gap analysis file

With Argument - File Specific or All

If $ARGUMENTS is "all":

  • File all gaps marked "FILE"

If $ARGUMENTS is specific gap ID:

  • File only that gap

GitHub Issue Creation

For each gap to file:

  1. Deduplication Check

    gh issue list --search "[gap title]" --label "pm:feature-request" --json number,title

    If >70% match exists: Show existing issue, ask to continue

  2. Create Issue using template from references/issue-template.md:

    gh issue create \
  --title "Feature: [Gap Name]" \
  --body "[Issue template filled]" \
  --label "pm:feature-request" \
  --label "[winning-label]" \
  --label "[priority-label]"

  3. Apply Labels:

    • WINNING 40+: winning:high, priority:now
    • WINNING 25-39: winning:medium, priority:next
    • WINNING <25: winning:low, priority:later

  4. Save Local Copy

    • Save to .pm/requests/[issue-number].md
    • Include GitHub issue number for reference

  5. Return Issue URLs to user

If gh CLI Unavailable

Output markdown formatted for manual GitHub issue creation.

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. 2d ago First seen · 76 lines · 0 tokens per session scan A 47d05f4ade69

Subscribe to this mod's changes

file is a command published in the GitHub repository ooiyeefei/ccc (483 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 487 once invoked, about $0.0000 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.

Code reviewDebugging
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens