manta-pr-workflow

manta-pr-workflow is a skill for Claude Code, Codex from antoinedc/MantaUI. It costs 71 tokens per session (4,774 once invoked), scanned A, original, MIT.

A prescribed workflow for implementing assigned issues in the MANTA software repository and preparing a draft pull request. It includes syncing the code, testing the change, and handing it to a reviewer.

In plain words
What is it for?
Use it to create a fresh branch, inspect relevant architecture guidance, implement an issue, run type checks and tests, push the branch, and open a draft pull request.
Why use it?
It keeps implementation work based on the latest main branch and records the checks needed before review.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /home/dev/projects/better-ui.

Good fit Use it to create a fresh branch, inspect relevant architecture guidance, implement an issue, run type checks and tests, push the branch, and open a draft pull request.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.

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.

agentmods badge for manta-pr-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/antoinedc/mantaui/manta-pr-workflow/github.svg)](https://agentmods.dev/skills/antoinedc/mantaui/manta-pr-workflow)
Your own site
<a href="https://agentmods.dev/skills/antoinedc/mantaui/manta-pr-workflow"><img src="https://agentmods.dev/badge/skills/antoinedc/mantaui/manta-pr-workflow/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.

agentmods 80×15 button for manta-pr-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/antoinedc/mantaui/manta-pr-workflow"><img src="https://agentmods.dev/badge/skills/antoinedc/mantaui/manta-pr-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,774 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.
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.1 $0.00071 $0.04774
Opus 5 $0.00036 $0.02387
Sonnet 5 $0.00014 $0.00955
Haiku 4.5 $0.00007 $0.00477

Measured 10d ago against content hash ae5ab3966a19, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

manta-pr-workflow 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 10d 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.

.multica/skills/manta-pr-workflow/SKILL.md · 356 lines

How it starts

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

manta-pr-workflow

The standard implementer workflow for the MANTA agents.

Steps

  1. multica repo checkout [email protected]:antoinedc/MantaUI.git inside your workdir. Never edit files outside the workdir. (A human-owned checkout at /home/dev/projects/better-ui bypasses isolation.)

  2. Sync main to origin/main BEFORE you branch (mandatory — stale-base antibody). A reused/cached workdir can hold a main that is days behind origin/main; branching off it makes your diff appear to delete files that were merged to origin/main after your stale checkout, producing phantom "you deleted X" review Blocks that no fix can resolve. Always:

    git fetch origin
    git checkout main
    git reset --hard origin/main      # workdir is disposable; make main == origin/main
    git checkout -b multica/BET-N-<slug>
    # Record the base you branched from, for the PR body (step 11):
    git rev-parse --short origin/main
    

    The recorded origin/main short-sha is your base SHA — put it in the PR body so the reviewer can confirm freshness in one glance.

  3. Read the issue. If it touches IPC, renderer, main process, preload, or server routes, re-read the matching architecture docs in the repo.

  4. Run the anti-spaghetti contract (below) before writing any new code. Search for an existing implementation first; the default move is to extend/reuse, not to add a parallel copy.

  5. Implement. Add or update tests under tests/ or __tests__/.

5b. Commit incrementally while you implement (BET-1445 — worktree-hijack insurance). A sibling session's multica repo checkout can resolve to YOUR worktree mid-run and hard-reset it (git reset --hard origin/main + branch switch), destroying uncommitted edits (killed the BET-1439 rerun, ~45 min). Checkouts are git worktrees of a shared bare clone, so committed work on your task branch survives a hijack — only the uncommitted delta is lost. So: commit to your task branch after every coherent unit and never leave more than a few minutes of work uncommitted (then push per step 8). And if your worktree suddenly looks reset/switched (unexpected origin/main HEAD, foreign branch, edits gone): run git branch --show-current, then recover — git checkout multica/BET-N-<slug> in place (or git worktree add <dir> multica/BET-N-<slug> if checkout is disturbed) — verify with git log that your commits are intact, redo only the lost delta, and CONTINUE. Do not assume the work is lost and restart from zero.

Read the full file on GitHub · 356 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. 10d ago First seen · 356 lines · 71 tokens per session scan A ae5ab3966a19

Subscribe to this mod's changes

manta-pr-workflow is a skill published in the GitHub repository antoinedc/MantaUI (12 stars, last pushed 4d ago), licensed MIT. It adds 71 tokens to every session and 4,774 once invoked, about $0.0004 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.