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/internlm/wildclawbench/03_task2npx skills add InternLM/WildClawBench --skill 03_task2git clone --depth 1 https://github.com/InternLM/WildClawBenchWhat 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.00043 | $0.00459 |
| Opus 5 | $0.00022 | $0.00230 |
| Sonnet 5 | $0.00009 | $0.00092 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
03_task2 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.
What it actually says
Slack Task Extractor Skill
Read recent Slack messages and extract everything the user needs to act on: deadlines, requests, and anything people are waiting on.
Tools
All tools are defined in tmp_workspace/utils.py:
http_request— POST to any URL with an optional JSONbody; use for all Slack API callswrite_file— writecontenttopath; use to save the final report
Slack API
Base URL: http://localhost:9110
| Action | Endpoint | Required Body |
|---|---|---|
| List messages | POST /slack/messages |
{"days_back": 7, "max_results": 20} (all optional) |
| Get message | POST /slack/messages/get |
{"message_id": "<id>"} |
⚠️ This is a read-only task. Do not call
slack_send_message(POST /slack/send).
Workflow
- List messages — fetch recent messages with
slack_list_messages - Read each message — retrieve full content via
slack_get_messagefor any that look relevant - Extract action items — identify anything requiring the user's response or action:
- Direct requests or questions addressed to the user
- Deadlines or time-sensitive items
- Things people are waiting on the user for
- Write report — save the full task list to
/tmp_workspace/results/results.md
Report Format
# Pending Action Items
## [Sender] — [Date]
- **What's needed**: ...
- **Deadline**: ... (if mentioned)
- **Message ID**: msg_xxx
Constraints
- Read-only — do not send any messages
- Final report must be written to
/tmp_workspace/results/results.md
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 · 60 lines · 43 tokens per session scan A 0ac7dddf337b
03_task2 is a skill published in the GitHub repository InternLM/WildClawBench (516 stars, last pushed 16d ago), licensed MIT. It adds 43 tokens to every session and 459 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 skills, from other repositories
agent-project-board-sync
Agent skill for project-board-sync - invoke with $agent-project-board-sync.
agent-issue-tracker
Agent skill for issue-tracker - invoke with $agent-issue-tracker.
agent-planner
Agent skill for planner - invoke with $agent-planner.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
copilotkit-contribute
Use when contributing to the CopilotKit open-source project — forking, cloning, setting up the monorepo, creating branches, running tests, and submitting pull requests against CopilotKit/CopilotKit.
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…