Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add slash9494/ai-config-sync-manager/plugin install config-managerWrote 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.
[](https://agentmods.dev/commands/slash9494/ai-config-sync-manager/paraphrase)<a href="https://agentmods.dev/commands/slash9494/ai-config-sync-manager/paraphrase"><img src="https://agentmods.dev/badge/commands/slash9494/ai-config-sync-manager/paraphrase.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00041 | $0.00690 |
| Opus 5 | $0.00020 | $0.00345 |
| Sonnet 5 | $0.00008 | $0.00138 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
paraphrase 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 8d 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.
What it actually says
If $ARGUMENTS is natural-language intent (Korean or English) instead of CLI flags, translate it into the matching paraphrase CLI flags before running. Mapping rules:
"X를 Y로 치환"/"X to Y"→--map "X=Y"(multiple mappings comma-separated:--map "Read=Inspect,Write=Emit")"codex에서 실행가능한 단어로 치환"/"host-strict 자동 치환"/"일반 paraphrase"→ no--map(uses bundledrules/paraphrase-map.json)- explicit agent/skill scope (e.g.
"repo-code-analyst만") →--include agents:<name>or--include skills:<name> "등록만"/"등록해줘"/"register only"/"파일은 그대로 두고 override만"/"이미 치환된 라인"/"pre-paraphrased"/"수동으로 치환된"→--register(skip the rewrite stage, append override entries directly when the effective map equates the diverging line pair)- Arguments that already start with
--→ passed through as-is
First run a dry-run preview (paraphrase defaults to dry-run unless --apply is given). When $ARGUMENTS looks like CLI flags or is empty, the CLI runs immediately; when it looks like natural-language intent, the bash branch prints a notice and you should translate it to flags using the mapping rules above, then re-invoke with the explicit flags:
!AI_CONFIG_SYNC_HOST=claude bash -lc 'case "$ARGUMENTS" in ""|--*) "${CLAUDE_PLUGIN_ROOT}/bin/ai-config-sync" paraphrase '"$ARGUMENTS"' ;; *) echo "[natural-language intent detected] $ARGUMENTS — translate to paraphrase CLI flags using the mapping rules above, then run the bash command at the bottom of this skill." ;; esac'
Confirmation flow:
- The slash command always shows a dry-run preview first.
- After reviewing the preview, ask the user in chat whether to apply.
- On the user's explicit yes, re-run this command with
--applyappended.
Before applying changes:
- Summarize the CLI output exactly; show which files and lines will be rewritten.
- Highlight tokens that have no paraphrase yet (CLI labels them
pendingTokens) and ask the user for explicit mappings before applying. - The CLI registers each rewritten line in
rules/paraphrase-overrides.json; verify the entries match the planned changes.
Apply only after the user explicitly confirms in chat:
AI_CONFIG_SYNC_HOST=claude "${CLAUDE_PLUGIN_ROOT}/bin/ai-config-sync" paraphrase $ARGUMENTS --apply
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.
- 8d ago First seen · 36 lines · 41 tokens per session scan A 5274927ca664
paraphrase is a command published in the GitHub repository slash9494/ai-config-sync-manager (36 stars, last pushed 3d ago), licensed MIT. It adds 41 tokens to every session and 690 once invoked, about $0.0002 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
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.
specify
Create or update the feature specification from a natural language feature description.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.