Browser4 is an AI-native browser engine that lets autonomous agents and people control real browsers, extract information from web pages, and automate tasks at scale. It combines browser interaction through a Rust CLI and MCP with deterministic selectors, machine-learning clustering, and language-model extraction. The catalogue entries provide skills and instructions for using Browser4.
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 platonai/Browser4 --skill organize-task-filesgit clone --depth 1 https://github.com/platonai/Browser4Wrote 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/platonai/browser4/organize-task-files)<a href="https://agentmods.dev/skills/platonai/browser4/organize-task-files"><img src="https://agentmods.dev/badge/skills/platonai/browser4/organize-task-files/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/platonai/browser4/organize-task-files"><img src="https://agentmods.dev/badge/skills/platonai/browser4/organize-task-files.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00049 | $0.00838 |
| Opus 5.5 | $0.00020 | $0.00335 |
| Sonnet 5.5 | $0.00010 | $0.00168 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
organize-task-files 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 1mo 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Organize Task Files
Manages .full.md (evaluation outputs) and .issues.md (extracted issues) files across the Coworker task state machine pipelines.
When to Use
- "organize task files"
- "show me what tasks are in each pipeline stage"
- "find unpaired .full.md and .issues.md files"
- "find duplicate task files"
- "find empty issues files (zero issues found)"
- "move task files from X to Y"
- "clean up the issues draft directory"
How It Works
- Scans
coworker/tasks/(issues, main) for.mdtask files - Parses filenames with pattern
YYYYMMDD-HHMMSS-taskname.{full,issues}.mdor plaintaskname.md - Groups by task name, detects pairs/dupes/orphans, classifies by pipeline stage
Usage
Run the bundled script:
python3 coworker/skills/organize-task-files/scripts/organize.py COMMAND [OPTIONS]
Commands
| Command | Description |
|---|---|
summary |
Overview of all pipelines: file counts per stage, type breakdown |
list |
List all task files with full paths, grouped by pipeline stage |
pairs |
Match .full.md ↔ .issues.md pairs; flag orphans |
dupes |
Find duplicate task names across directories and stages |
empty |
Find .issues.md files with "0 issues found" |
move |
Move matching files between pipeline stages (dry-run by default) |
Options
| Flag | Description |
|---|---|
--dir DIR |
Only scan a specific directory (default: all task dirs) |
--dry-run |
Show what would happen without making changes (default for move) |
--force |
Actually perform moves (use with move) |
--json |
Output as JSON for scripting |
Examples
# Overview of all pipelines
python3 coworker/skills/organize-task-files/scripts/organize.py summary
# Find unpaired files in issues draft
python3 coworker/skills/organize-task-files/scripts/organize.py pairs --dir issues/draft
# List all duplicate task names
python3 coworker/skills/organize-task-files/scripts/organize.py dupes
# Find empty .issues.md files (zero issues)
python3 coworker/skills/organize-task-files/scripts/organize.py empty
# Preview moving empty issues files to a discard directory
python3 coworker/skills/organize-task-files/scripts/organize.py move --dir issues/draft --filter empty --target coworker/tasks/issues/review/done/discard
# Actually perform the move
python3 coworker/skills/organize-task-files/scripts/organize.py move --dir issues/draft --filter empty --target coworker/tasks/issues/review/done/discard --force
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 89 lines · 49 tokens per session scan A c7d55c609d03
organize-task-files is a skill published in the GitHub repository platonai/Browser4 (1,161 stars, last pushed yesterday), licensed Apache-2.0. It adds 49 tokens to every session and 838 once invoked, about $0.0002 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-30.
Other skills, from other repositories
paperclip
Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.
paperclip-task-bridge
Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.
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…
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
review-my-team
Review a connected Paperclip team's agents, tasks, blockers and pending approvals when the user asks for a team summary or what needs attention.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.