Skip to content
Skills Library
AI & agents · Automation

agent-files

/agent-files

Use single-file Python agents (*_agent.py) as your own tools. You become the host - you list the agents, decide which to call, run them with run.py, and answer from their results. Use when the user hands you an agent file, a folder of them, or asks you to "run this agent", "be the brainstem", or "use my agents".

Repository
rar ↗
Licence
MIT
Last repository change
13.11.2026

Assessment and security

95/ 100Class: good
Format20 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
8
Scripts
5
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 5 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: brainstem_impact_agent.py, hebbian_synapse_agent.py, pain_receptor_agent.py, reflex_arc_agent.py, run.py

What it does and when to use it

Use single-file Python agents (*_agent.py) as your own tools. You become the host - you list the agents, decide which to call, run them with run.py, and answer from their results. Use when the user hands you an agent file, a folder of them, or asks you to "run this agent", "be the brainstem", or "use my agents".

Triggers from the description

run this agentbe the brainstemuse my agents
Original author description

Use single-file Python agents (*_agent.py) as your own tools. You become the host - you list the agents, decide which to call, run them with run.py, and answer from their results. Use when the user hands you an agent file, a folder of them, or asks you to "run this agent", "be the brainstem", or "use my agents".

How it works

  1. The loop
  2. Rules
  3. What's in this folder
Original SKILL.md headings · 45 lines, 377 words
SKILL.md preview
---
name: agent-files
description: Use single-file Python agents (*_agent.py) as your own tools. You become the host - you list the agents, decide which to call, run them with run.py, and answer from their results. Use when the user hands you an agent file, a folder of them, or asks you to "run this agent", "be the brainstem", or "use my agents".
---

# Agent files: you are the host

An agent file is one Python file ending in `_agent.py`. It holds a class with:
- `metadata` - a function schema: `name`, `description`, `parameters`.
- `perform(**kwargs)` - does the work and returns text.

Anything that reads the schema, picks a tool and calls `perform()` is a host.
In this skill, **you** are that host. No server, no install.

## The loop

1. **See your tools.** Run:
   `python3 run.py list`
   (or `python3 run.py list <folder>` for the user's own folder of agents).
   Read each tool's `description` - that is how you decide when to use it.
   If the output has `context`, treat it as background for the conversation.
   If it has `broken`, tell the user which file failed and why.
2. **Decide.** For the user's request, choose zero, one or several tools,
   exactly as you would choose any function to call. If none fits, just answer.
3. **Fire.** Run:
   `python3 run.py fire <Name> '<json arguments>' [folder]`
   Arguments must match the tool's `parameters`. Use `'{}'` for none.
4. **Read and continue.** Use the result. Fire another tool if it helps,
   up to 3 rounds per request, then answer the user in plain words.
5. **New files are new tools.** If the user adds or changes an agent file,
   the next `list` or `fire` sees it. No restart.

## Rules

- Run `list` before the first `fire` in a conversation, and again after any
  agent file changes.
- Never edit an agent file to make it work; report the error instead.
- Read an agent file before its first run if you didn't write it or the user
  didn't vouch for it. It is code running on their machine.
- Show the user what you fired, in one line (`Fired: Name {args}`), then the answer.
- If you can't run shell commands, read the agent file and tell the user the
  exact `fire` command to run, then continue from the result they paste back.

## What's in this folder

- `run.py` - the only machinery: lists and fires agents. Standard library only.
- the `*_agent.py` files - the agents (they can also live in an `agents/` folder).
  run.py has the shared base class built in. Drop in any `*_agent.py` to add a tool.
Files in this package (8)
  • README.md 1 KB
  • SKILL.md 2 KB
  • brainstem_impact_agent.py 8 KB
  • hebbian_synapse_agent.py 6 KB
  • pack.json 2 KB
  • pain_receptor_agent.py 3 KB
  • reflex_arc_agent.py 5 KB
  • run.py 5 KB

Versions

RepositoryScoreLicence
This page · kody-w/rar95MIT
23blocks-OS/ai-maestro-plugins100MIT

Database snapshot: 13.11.2026 · package version cbdc48a7df69 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 93aibast-brainstem
    Read once, then never again. Lets you use and build Brainstem agents from the AIBAST Agents Library: you keep an agents/ folder, load every agent file in it fresh each turn, bring agents from the library catalog by name, build and test new ones, and answer in a Brainstem's chat…
  • 93rapp
    Read once, then never again. Makes you RAPP compatible for good: you become a Brainstem that keeps an agents/ folder, loads every agent file in it fresh each turn, brings new ones by a seven-word chant, and answers in a Brainstem's chat shape. Use when the person says RAPP,…
  • 91create-agent
    Create new agents for the code-forge application. Agents are stored as .md files in the <cwd>/.forge/agents directory with YAML frontmatter (id, title, description, reasoning, tools, user_prompt) and markdown body containing agent instructions. Use when users need to add new…
  • 100aixplain-agent-builder
    Build, configure, deploy, run, debug, export, verify, and update aixplain agents from a user's problem or intent using the Python SDK v2. Use for single agents, teams, marketplace tools, integrations, custom Python tools, runtime Code Execution, knowledge, sessions, budgets, and…
  • 100custom-agent-definitions
    Write and configure custom agent definitions in Claude Code agents/ directory. Use when creating an agent .md file, defining a specialized agent, or configuring agent tools.
  • 100write-agents-files
    Use when setting up or improving agent instructions in AGENTS.md, CLAUDE.md or other coding agents instructions files.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.