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.
npx agentmods add skills/joymin5655/agent/wrapnpx skills add joymin5655/Agent --skill wrapgit clone --depth 1 https://github.com/joymin5655/AgentWhat 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 | $0.00068 | $0.01598 |
| Opus 5 | $0.00034 | $0.00799 |
| Sonnet 5 | $0.00014 | $0.00320 |
| Haiku 4.5 | $0.00007 | $0.00160 |
Grade A, and why
wrap 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.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wrap
Goal
Move from "code written and tested locally" to "PR open on GitHub" in one skill invocation, with all the safety gates intact.
Modes
| Mode | What it does | Trigger |
|---|---|---|
/wrap |
Commit + open PR. User pushes manually. | Default. |
/wrap --auto-push |
Commit + push + open PR. User merges. | Explicit. |
/wrap --auto-merge |
Full chain via core/infra/auto-ship.sh. |
Explicit. |
--auto-merge requires all 4 trigger conditions from
rules/policy/actions-billing-admin-merge.md to hold.
Steps
Reviews happen BEFORE wrapping — for a multi-vendor opinion on the diff, run
/council-review --stagedfirst (skills/council-review/SKILL.md).
1. Pre-flight checks (gates)
Run in order; any failure aborts before the commit.
a. gitleaks on staged diff:
gitleaks protect --staged --redact -v --config=gitleaks.toml --no-banner
Before trusting a clean result, confirm the gate is actually live with the fire drill (W-3) — it plants a synthetic secret matching the repo's own rule and asserts gitleaks catches it, so a misconfigured allowlist can't give a false all-clear:
bash core/infra/gitleaks-fire-test.sh # PASS = gate live; FAIL = misconfigured; exit 2 = gitleaks absent (SKIP)
a2. Remote-URL credential scan (W-3) — a token baked into the push remote's
URL lives in .git/config, invisible to the content scanners above:
git remote get-url origin | python3 core/git-hooks/scan-remote-url.py
Nonzero exit = the remote URL embeds a credential; strip it before pushing.
(The pre-push hook also runs this, but checking here fails earlier.)
a3. Memory-pollution guard — a memory plugin's session-context dump
injected into a tracked instruction file (e.g. AGENTS.md) must never
reach a commit:
bash core/tests/memory-pollution-guard.sh
FAIL = revert the injected block (git checkout -- <file>) before committing.
b. Whitelist path scan — only files inside allowed paths should be
staged. Allowed paths default to anything except secrets/,
.env* (excl. .env.example). Override via hook-config.yml.
c. Risk-area scan — for each of the 5 risk areas
(rules/policy/security-guards.md):
data(e.g.,migrations/*.sql) → ABORT, user must drive.secrets→ ABORT.deploy(function bundles) → ABORT, user must drive.payment→ ABORT, user must drive.domain-output→ advisory; if net removal, ABORT. d. Council-scale pre-merge check — run the threshold script, resolved from the plugin cache or the checkout (never bare cwd-relative — a plugin install has nocore/under$PWD):
bash "${CLAUDE_PLUGIN_ROOT:-$PWD}/core/infra/council-threshold.sh" --staged
A missing script is not a pass: report the check as SKIPPED (step 1's
"a skipped gate is reported as skipped" rule) rather than reading its
nonzero exit as "not council-scale". Exit 10 (line/file threshold or
a risk-area path) AND no council/degrade review happened this session for
this diff (no .agent/workers/*-review.md capture, no single-vendor
degrade note) → recommend /council-review --staged and confirm with the
user before committing solo. This is advisory, not a gate abort — the user
can proceed anyway; it exists so a council-scale diff doesn't slip into a
commit on the strength of a Claude-only review that
council-escalation-gate.py never got a chance to catch (e.g. edits made
without a Task/Agent dispatch).
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.
- 2d ago First seen · 158 lines · 68 tokens per session scan A cba1104da7d8
wrap is a skill published in the GitHub repository joymin5655/Agent (2 stars, last pushed 8d ago), licensed MIT. It adds 68 tokens to every session and 1,598 once invoked, about $0.0003 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.
Other skills, from other repositories
regex-mastery
Use this skill when writing regular expressions, debugging pattern matching,optimizing regex performance, or implementing text validation. Triggers on regex, regular expressions, pattern matching, lookahead, lookbehind, named groups, capture groups, backreferences, and any task requiring text pattern matching.
pr-delivery-loop
The implementation-lane standard for delivering a PR across the Avibe repositories (avibe, avibe-backend, avibe-docs, avault, and vault-sandbox) — branch/scope rules, contracts, Codex-bot review-loop discipline, and close-out criteria. Use this skill for every implementation task in these repos, regardless of agent…
release-notes
Generates concise release notes.
shell-scripting
Use this skill when writing bash or zsh scripts, parsing arguments, handling errors, or automating CLI workflows. Triggers on bash scripting, shell scripts, argument parsing, process substitution, here documents, signal trapping, exit codes, and any task requiring portable shell script development.
github-release-create
Create a GitHub release from a tag with release notes.
github-release-list
List GitHub releases (tags, assets, published dates).