create-agent skillA
create-agent is agent-read markdown (skill) from tailcallhq/forgecode: 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 agents, modify existing agents, or understand the agent file structure..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified before it reaches your agent: the main file against the SHA-256 recorded here, the others against the git hashes of its source commit. The deterministic audit below grades the latest version, and the same checks always give the same file the same grade.
What the file says
{{{{raw}}}}
# Create Agents
Create and manage agents for the code-forge application. Agents are specialized AI assistants with specific capabilities, tools, and behaviors.
## File Location
**CRITICAL**: All agent files must be created in the `<cwd>/.forge/agents` directory, where `<cwd>` is the current working directory of your code-forge project.
- **Directory**: `<cwd>/.forge/agents`
- **File format**: `{agent-id}.md`
- **Example**: If your project is at `/home/user/my-project`, agents go in `/home/user/my-project/.forge/agents/`
This is the only location where forge will discover and load custom agents.
## Agent File Structure
Every agent file must have:
1. **YAML Frontmatter** (required):
- `id`: Unique agent identifier
- `title`: Agent display name
- `description`: Detailed description of what the agent does
- `reasoning`: Configuration with `enabled: true/false`
- `tools`: List of tools the agent can use
- `user_prompt`: Template for user context
2. **Agent Body** (required):
- Agent identity and purpose
- Core principles
- Capabilities
- Methodology
- Best practices
- Limitations and boundaries
### Example Agent File
…Read the whole file at its exact version.
How to install
mdr add tailcallhq/forgecode/create-agent@git:20260126.0427bf8mdr add tailcallhq/forgecode/create-agent@sha256:74001edd054d4f57Pin to a label to follow the author's releases, or to a sha256 for exact bytes. Either way the resolved hash is written to mdr.lock, and mdr install fetches those bytes again and checks them, so it installs them exactly or fails.
[](https://markdownregistry.com/a/art_7seokmoztdsjasit)
2 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (29125 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
tailcallhq/forgecode · 7,637 stars · license Apache-2.0 · pushed 2026-09-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7seokmoztdsjasit GET https://markdownregistry.com/api/v1/resolve?ref=tailcallhq/forgecode/create-agent GET https://markdownregistry.com/api/v1/blob/74001edd054d4f57863ac9586923a7e9d246e0633b32c286b8acbe08bbae6b83
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from tailcallhq/forgecode
Every file in tailcallhq/forgecode