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 skills add Jaxton07/jax-skills --skill channel-pickupgit clone --depth 1 https://github.com/Jaxton07/jax-skillsWrote 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/jaxton07/jax-skills/channel-pickup)<a href="https://agentmods.dev/skills/jaxton07/jax-skills/channel-pickup"><img src="https://agentmods.dev/badge/skills/jaxton07/jax-skills/channel-pickup/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.
<a href="https://agentmods.dev/skills/jaxton07/jax-skills/channel-pickup"><img src="https://agentmods.dev/badge/skills/jaxton07/jax-skills/channel-pickup.svg" alt="Reviewed on agentmods" width="80" 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.00099 | $0.00876 |
| Opus 5.5 | $0.00040 | $0.00350 |
| Sonnet 5.5 | $0.00020 | $0.00175 |
| Haiku 4.5 | $0.00010 | $0.00088 |
Grade A, and why
channel-pickup 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 2mo 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
接手频道任务（实施会话用）
你没有上一个会话的记忆，也不需要。频道目录 + 设计文档是唯一事实来源，不要找用户复述背景。
开工三步（顺序固定）
- 读频道：
.local/agent-work/channel/<主题>/HANDOFF.md（用户没给主题就ls .local/agent-work/channel/列出让用户选）。若存在REVIEW.md也一并读——里面的意见是你工作的一部分。 - 读文档：按 HANDOFF 指定顺序读 spec（
.local/docs/design/spec/）→ plan（.local/docs/design/plan/）→ 项目根AGENTS.md/CLAUDE.md+ 项目索引（如有.local/docs/INDEX.md）。 - 采信事实表：HANDOFF 里的「已验证事实」是上一会话读源码考证过的，直接用，禁止重复考证；真要推翻，先回 channel 留言说明证据。
执行纪律
- 按 plan 阶段推进；阶段 0 冒烟验证先行，其断言是后续所有决策的地基。
- plan/spec 与代码现状冲突、或冒烟断言失败 → 停下来写进
IMPL-NOTES.md并告知用户，不要自由发挥绕过。 - 遇到 HANDOFF 列的「待决策点」：自行决策，决策与理由记入
IMPL-NOTES.md。 - 项目通用纪律全适用（以仓库根
AGENTS.md/CLAUDE.md约定为准，有踩坑记录先读）。 - 测试完毕后关闭过程中起的服务和进程（dev 实例、冒烟脚本、临时端口监听等）。
沟通协议（只认文件）
IMPL-NOTES.md：进度、卡点、决策，追加式、倒序（最新在最上）、每条带日期时间并标注所属阶段。DONE.md（完成时写）：验收清单逐项打勾 + 改动文件清单 + 自测记录（手测每步的实际结果，不是「应该没问题」）。REVIEW.md：review 方的意见入口；每次复工前先读，逐条回应（改代码或在 IMPL-NOTES 说明不改的理由）。- 完成后提醒用户：DONE.md 已就绪，等 review。
收尾（DONE.md 之前必做）
- 项目自带的 lint / typecheck / test 全绿（按
package.jsonscripts 或项目等价命令），输出摘要贴进 DONE.md。 - 若项目维护了
.local/docs/INDEX.md之类的代码索引：把新增/删除/改名的代码文件、变化的导出与签名补进对应清单。spec/plan/channel 文档不要加进索引（索引只标目录不标文件，文档会不定期清理）。 - 若实施中发现 spec/plan 过时（决策被推翻、边界调整）：在 channel 留言说明，不要顺手改 spec——spec 的修改权在发起会话/用户。
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.
- 2mo ago First seen · 37 lines · 99 tokens per session scan A 21782ec066df
channel-pickup is a skill published in the GitHub repository Jaxton07/jax-skills (1 stars, last pushed 2mo ago), licensed MIT. It adds 99 tokens to every session and 876 once invoked, about $0.0004 per session on Opus 5.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
strategic-alignment
Use when teams pull in different directions, OKRs don't connect or departments optimize locally. Maps the strategy cascade and finds orphan goals and silos with alignmentchecker.py.
process-mapper
Use when documenting an end-to-end business process (procurement, onboarding, handoffs) and finding where work waits. Maps it with processdocumenter.py, measures stages with cycletimeanalyzer.py and finds bottlenecks with bottleneckdetector.py.
change-management
Use when rolling out a reorg, pivot, tool switch, leadership change or product kill. Plans it with ADKAR, communication templates and resistance patterns.
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
scenario-team-admin
Use when administering a Scenario team from an agent through MCP: restricting which models a team or project can run (model access control, allowlist, blocklist), inviting or removing team and project members, changing roles, capping a member's Creative Unit spend, creating or deleting projects, auditing API keys and…