agentmods.dev

push

A command for publishing a single draft skill capsule to GitHub Gist and adding it to a shared discovery index.

In plain words
What is it for?
Selecting a local draft, previewing privacy findings, and pushing that draft to the FragCap registry.
Why use it?
It provides a process for checking authentication, reviewing possible personal information, and choosing the capsule's visibility before publishing.

Skill for Claude CodeCodex

2 5mo ago A scan 28 tokens original MIT
View the source file fragcap/plugin
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 skills/fragcap/plugin/push
Any agent
npx skills add fragcap/plugin --skill push
Clone the repo
git clone --depth 1 https://github.com/fragcap/plugin

Made for: Claude Code, Codex.

Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 702 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.00028 $0.00702
Opus 5 $0.00014 $0.00351
Sonnet 5 $0.00006 $0.00140
Haiku 4.5 $0.00003 $0.00070

Measured yesterday against content hash 37708143b269, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

skills/push/SKILL.md · 69 lines

How it starts

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

Push Capsule

Push a single draft capsule (SKILL.md) to GitHub Gist and register it in the central FragCap registry.

Script Convention

FRAGCAP_DATA="${CLAUDE_PLUGIN_DATA}" node "${CLAUDE_PLUGIN_ROOT}/scripts/<n>.mjs" [args]

On Windows/PowerShell, use $env:FRAGCAP_DATA="..." syntax instead.

If a script exits with a non-zero code or returns { error: "..." }, stop immediately and surface the error to the user. Never silently retry with a different command or skip the step.

When to Activate

  • User runs /fragcap:push or /fragcap:push <draft-id>
  • User explicitly asks to push a specific draft

Flow

  1. Auth gate — run auth-status.mjs. Not authenticated → direct to /fragcap:auth and stop.

  2. Select draft:

    • If $ARGUMENTS is provided, use it as the draft ID directly.
    • Otherwise, run list-drafts.mjs and show a numbered list. Present options inline — user replies with a number: 
      [1] <problem summary>  [2] <problem summary>  ...
    • If no drafts exist: "No local drafts to push. Ask Claude to generate a capsule draft first."

  3. PII preview — run preview-pii.mjs <draft-id>.

    • Show findings with risk levels and suggested replacements.
    • If findings exist, present a confirmation inline: 
      [1] Proceed anyway  [2] Cancel
    • If clean: "No PII detected."

  4. Visibility — present options inline, do not ask the user to type:

    [1] anonymous (default) — author replaced with hash, PII auto-stripped
[2] attributed — published with your GitHub username

  5. Gist scope — present options inline:

    [1] public (default) — searchable by others, registered in central index
[2] secret — unlisted, not registered in index

  6. Push — run push.mjs <draft-id> <visibility> <scope> where scope is public or secret.

  7. Result:

    • Success: show the Gist URL, public/secret status, and registry status. Mention that others can install this capsule with /fragcap:install <gist-id>.
    • General failure: "Push failed: {error}. Your draft is still saved locally — try again later."
    • Public registration failure (response contains suggest_secret: true):
      • The public Gist has already been rolled back (deleted) automatically.
      • Show the error and message fields from the response.
      • Present inline options: 
        [1] Upload as secret instead  [2] Cancel — keep draft locally
      • If user picks [1]: re-run push.mjs <draft-id> <visibility> secret.

Read the full file on GitHub · 69 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. yesterday First seen · 69 lines · 28 tokens per session scan A 37708143b269

Subscribe to this mod's changes

push is a skill published in the GitHub repository fragcap/plugin (2 stars, last pushed 5mo ago), licensed MIT. It adds 28 tokens to every session and 702 once invoked, about $0.0001 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-31.

claude-code-plugin
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens