add-agent
Skill253 starsChanged 5 months agoMITView on GitHub
Use when adding or updating an agent adapter in the Exgentic repository. Follow the repository agent principles, separate lightweight config from heavy execution logic, isolate third-party dependencies behind lazy imports, adapt to any benchmark contract without requiring benchmark changes, and validate the adapter with representative smoke tests before finishing.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- venkateshv1266/pi-harnesstheir own version, first seen Nov 1, 2026
- chacosoldier/compabobtheir own version, first seen Oct 23, 2026
- axrmxv/claude-configtheir own version, first seen Oct 13, 2026
- FISHers6/clawBrotheir own version, first seen Oct 8, 2026
- rgoerwit/ai-investment-agenttheir own version, first seen Oct 8, 2026
- mattolson/agent-sandboxtheir own version, first seen Oct 8, 2026
Used with
Projects with it also use setup.
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.
VercelSkillsetup
Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".
Also in 3 projects that use this
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- mattolson/agent-sandbox★ 212same name
- BerriAI/litellm-skills★ 84same name
- rgoerwit/ai-investment-agent★ 71same name
- chacosoldier/compabob★ 34same name
- FISHers6/clawBro★ 28same name
- venkateshv1266/pi-harness★ 2same name
- axrmxv/claude-config★ 1same name
- theopengroup/rune-harness★ 1same name
- tjg37/ironclaw★ 1same 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 repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- frontend/CLAUDE.mdCLAUDE.md
- frontend/packages/app/CLAUDE.mdCLAUDE.md
- frontend/packages/config/CLAUDE.mdCLAUDE.md
- frontend/packages/shared/CLAUDE.mdCLAUDE.md
- frontend/packages/ui/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- android-testerSkill
- add-benchmarkSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 3 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when working on agent adapters in the Exgentic repository.
- Very specific: line 25
If the agent depends on heavy third-party libraries (litellm, smolagents, openai SDK, etc.), put the Agent in one file and the …
- Very specific: line 33
Add requirements.txt for agent-specific dependencies.
- Very specific: line 36
Add setup.sh if non-pip setup is needed.
- Very specific: line 37
Place it next to the agent module.
- Very specific: line 40
Add a RegistryEntry to the AGENTS dict.
- Distinctive: line 43
Check registry loading, dependency isolation, at least one end-to-end benchmark run, cost reporting, and cleanup.
- Distinctive: line 58
Before finishing, run at least:
“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
Add Agent
Use this skill when working on agent adapters in the Exgentic repository.
First read
Start with:
docs/adding-agents.mdsrc/exgentic/core/agent.pysrc/exgentic/core/agent_instance.pysrc/exgentic/interfaces/registry.py
Then inspect the most relevant existing adapters:
src/exgentic/agents/litellm_tool_calling/litellm_tool_calling_agent.py+instance.py(split pattern: heavy deps in separate file)src/exgentic/agents/cli/claude/agent.py(light pattern: everything in one file)
Workflow
- Decide whether to split files.
If the agent depends on heavy third-party libraries (litellm, smolagents, openai SDK, etc.), put the Agent in one file and the AgentInstance in
instance.py. If deps are light, keep both in a single file. - Implement the Agent class first.
Subclass
Agent. Declaredisplay_nameandslug_nameasClassVar[str]. Add user-facing config fields. Implement_get_instance_class()with a lazy import. Implement_get_instance_kwargs()to translate config and the benchmark contract into instance constructor kwargs. - Implement the AgentInstance class.
Subclass
AgentInstance. Acceptsession_idplus the kwargs from_get_instance_kwargs(). Callsuper().__init__(session_id). Implementreact()as the core decision loop andclose()for cleanup. Optionally overridestart()andget_cost(). - Add
requirements.txtfor agent-specific dependencies. List only packages not already in the base exgentic install. Place the file in the agent's package directory;RunnerMixindiscovers it automatically. - Add
setup.shif non-pip setup is needed. Place it next to the agent module;RunnerMixindiscovers it automatically. - Register the agent in
src/exgentic/interfaces/registry.py. Add aRegistryEntryto theAGENTSdict. Ensureslug_nameanddisplay_namematch the class exactly. - Validate the adapter as an agent, not just as code. Check registry loading, dependency isolation, at least one end-to-end benchmark run, cost reporting, and cleanup.
Non-negotiable rules
- The Agent file must be importable without installing agent-specific packages.
_get_instance_class()must use a lazy import to isolate heavy deps._get_instance_kwargs()must faithfully pass the benchmark contract (task, context, actions, session_id) through to the instance.- The instance constructor must call
super().__init__(session_id). react()must returnNonewhen the agent decides it is done.close()must not raise exceptions.slug_nameanddisplay_namein the registry entry must exactly match the class values.- The agent must adapt to the benchmark, never the other way around.
Validation
Before finishing, run at least:
python -m py_compileon changed agent filespre-commit run --files ...git diff --check
Also confirm:
load_agent("slug_name")succeeds from a Python shell- The Agent file imports cleanly without agent-specific packages installed
- At least one benchmark runs end to end with the new agent
close()completes without errorget_cost()returns a valid report
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.

