agent-tools
Skill9 starsChanged 53 days agoMITView on GitHub
Names and purpose of every agent tool. Load to list tools.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- BrightGold70/skillstheir own version, first seen Nov 8, 2026
- will-ness-ai/skillstheir own version, first seen Oct 25, 2026
- jratlee/FDItheir own version, first seen Oct 11, 2026
- AngelescuCiprian/claude-skillstheir own version, first seen Aug 22, 2026
- nikunj812/claude-skilltheir own version, first seen Jul 1, 2026
- tysongreenan/claude-code-webapp-boilerplatetheir own version, first seen Apr 8, 2026
Used with
Projects with it also use brand-guidelines.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JetBrainsSkillbrand-guidelines
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Also in 3 projects that use this
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- will-ness-ai/skills★ 170same name
- tysongreenan/claude-code-webapp-boilerplate★ 2same name
- BrightGold70/skills★ 1same name
- Typeless-Git/skills★ 1same name
- AngelescuCiprian/claude-skills★ 0same name
- jratlee/FDI★ 0same name
- nikunj812/claude-skill★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- camoufox-antidetectSkill
- context-budgetSkill
- telegram-markdownSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 62
Use it instead of guessing when the decision is theirs
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
The agent has 78 tools. Grouped by what they do; read-only ones do not need approval, mutating ones do.
Shell & execution
execute_bash— a shell in your workspace, blocked patterns refusedexecute_python— python3, output cappedexecute_node—node:vmsandbox, synchronous, no fs/child_processjob_start/job_status/job_output/job_kill— long-running work that outlives the 30s tool budgetgit— git in the workspace, refuses force/reset --hard/clean -fxsysinfo— host, runtime, memory, load
Files
read_file/write_file/edit_file/list_dirmulti_edit— N edits to one file, atomic: all land or none dodiff_review/diff_reject— numbered hunks, reject one keep the restast_edit— identifier rename that skips strings and commentsrun_tests— auto-detects pytest/jest/go/cargocompile_run— rustc/go/gcc with line:column errorssend_document— deliver a workspace file to the chat
Finding things
grep— regex across the workspace; ripgrep when present, a JS fallback when not.path:line:matchoutput, cappedglob— files by name pattern, newest first, node_modules excluded
Memory & knowledge
remember/recall/forget— durable facts across /reset and restartrecord_lesson/recall_lesson— a failed approach and the fixrecord_decision— why one path was taken, readable via /whyscratchpad_write/read/list/delete— working state out of the context window
Browser (Camoufox, session per chat)
browser_navigate/browser_snapshot(@eN refs) /browser_readbrowser_click/browser_type(dangerous)browser_search/browser_closebrowser_wait/browser_scroll/browser_keyboard/browser_formbrowser_extract/browser_console/browser_screenshot/browser_tabs
Delegation
delegate_task— a subagent with its own context window for an independent subtask. Read-only tools by default, max depth 2.
Observability
trace_export— the full trace of a turn as JSON/Markdown/textcost_report— spend breakdown per model and per tool
Port forwarding (like VS Code)
tunnel_open/tunnel_list/tunnel_close— give a localhost server a URL the user can open. Relay URLs carry a secret path token; an open port is not a reachable service
Talking to the human
ask_user— stop and wait for an answer. Choice buttons or a typed reply. Use it instead of guessing when the decision is theirscode_indexthensemantic_code_search— find code by meaning instead of grepping blind. Index once, reuse. Prefer this over reading three files whole when you only need the one function.code_symbols— the map of what is in a file, before you read it.dependency_graph— what breaks if you edit this file. Check before a refactor, not after.dead_code_scan— candidates for removal; always verify before deleting. — the session task list, visible as /todo- the user can drop a
.zipor code file into the chat; it lands in the workspace as real files, so tell them to do that instead of pasting a wall of code./undorestores the last change you made in their workspace — offer it when a refactor goes sideways.
Choose by blast radius: read first (read_file, list_dir, browser_read),
then act (multi_edit over repeated edit_file, job_start for anything
over a few seconds). Never rm in bash when edit_file will do.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

