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/breakingmind/claude-external-plugins-line/configurenpx skills add breakingmind/claude-external-plugins-line --skill configuregit clone --depth 1 https://github.com/breakingmind/claude-external-plugins-lineWrote 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/skills/breakingmind/claude-external-plugins-line/configure)<a href="https://agentmods.dev/skills/breakingmind/claude-external-plugins-line/configure"><img src="https://agentmods.dev/badge/skills/breakingmind/claude-external-plugins-line/configure.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 | $0.00047 | $0.00873 |
| Opus 5 | $0.00023 | $0.00436 |
| Sonnet 5 | $0.00009 | $0.00175 |
| Haiku 4.5 | $0.00005 | $0.00087 |
Grade A, and why
configure 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 4d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/line:configure — LINE Channel Setup
Writes LINE credentials to ~/.claude/channels/line/.env and orients the
user on access policy. The server reads both files at boot.
Arguments passed: $ARGUMENTS
Dispatch on arguments
No args — status and guidance
Read both state files and give the user a complete picture:
-
Credentials — check
~/.claude/channels/line/.envforLINE_CHANNEL_ACCESS_TOKENandLINE_CHANNEL_SECRET. Show set/not-set; if set, show first 10 chars masked (e.g.ABCdef1234...). -
Webhook port — show
LINE_WEBHOOK_PORT(default: 3000). -
Access — read
~/.claude/channels/line/access.json(missing file = defaults:dmPolicy: "pairing", empty allowlist). Show:- DM policy and what it means in one line
- Allowed users: count and list IDs
- Pending pairings: count, with codes and user IDs if any
-
What next — end with a concrete next step based on state:
- No credentials → "Run
/line:configure token <token>then/line:configure secret <secret>with credentials from LINE Developers Console." - Credentials set, nobody paired → "Message your LINE bot. It replies
with a code; approve with
/line:access pair <code>." - Credentials set, someone paired → "Ready. Message your LINE bot to reach the assistant."
- Always remind: LINE requires a public HTTPS webhook — use ngrok or
Cloudflare Tunnel to expose port 3000 (or
LINE_WEBHOOK_PORT).
- No credentials → "Run
Push toward lockdown — always. Once IDs are captured via pairing,
switch to allowlist policy. Offer to run /line:access policy allowlist.
token <value> — save Channel Access Token
- Treat the argument as the token (trim whitespace).
mkdir -p ~/.claude/channels/line- Read existing
.envif present; update/add theLINE_CHANNEL_ACCESS_TOKEN=line, preserve other keys. Write back, no quotes around the value. - Confirm, then show the no-args status.
secret <value> — save Channel Secret
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.
- 4d ago First seen · 92 lines · 47 tokens per session scan A 4dfd50bc62d1
configure is a skill published in the GitHub repository breakingmind/claude-external-plugins-line (9 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 873 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…