CREATING_AGENTS

A guide for defining AI assistants as configuration files, including their instructions, inputs, available tools, and execution settings. These assistants can perform tasks through MCP, a standard connection for external tools.

In plain words
What is it for?
Use it to create file-analysis or other task-specific agents, define their inputs and tool access, choose execution limits, and prepare them for deployment.
Why use it?
It provides a repeatable structure for building agents instead of configuring each one informally or from scratch.

Agent

Install

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.

agentmods
npx agentmods add agents/cloudshipai/station/creating_agents
Clone the repo
git clone --depth 1 https://github.com/cloudshipai/station
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,795 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.03795
Opus 5 $0.00000 $0.01898
Sonnet 5 $0.00000 $0.00759
Haiku 4.5 $0.00000 $0.00380

Measured yesterday against content hash 8065e3b22fe0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

CREATING_AGENTS 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 yesterday.

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.

docs/agents/CREATING_AGENTS.md · 652 lines

How it starts

The opening of the file, as written. The whole thing — 652 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Creating Station Agents

Station agents are intelligent AI assistants that can execute tasks using MCP (Model Context Protocol) tools. This guide covers creating, configuring, and deploying agents.

Agent Fundamentals

What is a Station Agent?

A Station agent consists of:

  • Dotprompt Configuration: YAML frontmatter with metadata and input schema
  • Multi-role Prompt Structure: System and user role definitions
  • Tool Access: MCP tools available to the agent
  • Execution Context: Environment and variable configuration

Agent File Structure

Agents are defined in .prompt files with this structure:

---
metadata:
  name: "File Analyzer Agent"
  description: "Analyzes files and directories for insights"
  tags: ["filesystem", "analysis"]
model: gpt-4o-mini
max_steps: 8
tools:
  - "__read_text_file"
  - "__list_directory"
  - "__get_file_info"
  - "__search_files"
input:
  schema:
    type: object
    properties:
      userInput:
        type: string
        description: User input for the agent
      file_path:
        type: string
        description: Path to file or directory to analyze
      analysis_type:
        type: string
        enum: ["basic", "detailed", "security"]
        default: "basic"
    required:
      - userInput
---

{{role "system"}}
You are an expert file analysis agent. When given a file or directory path,
you analyze its contents and provide insights about:
- File types and structure
- Content summaries  
- Potential issues or improvements
- Organization suggestions

Use the provided tools to examine files and directories thoroughly.
Be thorough but concise in your analysis.

{{role "user"}}
{{userInput}}

**Analysis Target:** {{file_path}}
**Analysis Type:** {{analysis_type}}

Creating Agents

Method 1: Interactive CLI Creation

# Start interactive agent creation
stn agent create

# Follow prompts for:
# - Agent name and description
# - Environment selection
# - Tool selection
# - Prompt definition

Read the full file on GitHub · 652 lines

Changes

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.

  1. yesterday First seen · 652 lines · 0 tokens per session scan A 8065e3b22fe0

Subscribe to this mod's changes

CREATING_AGENTS is an agent published in the GitHub repository cloudshipai/station (429 stars, last pushed 7mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,795 tokens. 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.

Related

Other agents, from other repositories

demo-site

Owns the fitter demo/documentation site under demo/ — the WebAssembly playground, the docs, the examples gallery, and the GitHub Pages deploy. Use for any work on demo/index.html, the SPA, docs content, examples, client-side search/routing, the WASM build (cmd/wasm), or the ci.yaml pages job. Trigger phrases: "demo…

PxyUp/fitter · 97 tokens

deploy-reviewer

Reviews fold's deployment surface — the Helm chart's rendered output, Kubernetes security posture, the four Dockerfiles, and the compose stack — for what only shows up in the manifest rather than in the templates. Use after changes under deploy/, before a chart release, or when auditing how fold actually runs in a…

fold-run/fold · 67 tokens

release-verifier

Verifies a published fold release end to end from the outside — archives, checksums and their cosign signature, SBOMs, the four ghcr images, the OCI chart, and every sigstore attestation. Use after a tag's release workflow goes green, before announcing a release, or when someone asks whether a published artifact is…

fold-run/fold · 74 tokens

mcp-spec-auditor

Audits fold against the normative MCP specification for the pinned revision — method shapes, required fields and headers, error-code allocation, caching and intermediary rules, and deprecations on the clock. Use when a change touches wire behavior, when a new protocol revision ships, or before bumping the conformance…

fold-run/fold · 73 tokens

gateway-reviewer

Reviews fold changes against the gateway's architectural invariants — pipeline order, snapshot-based reload state, audit as the single exit door, the invisibility rule, the minted error-code registry, and proxy-path allocation discipline. Use proactively after any non-trivial change to gateway/, auth/, policy/, or…

fold-run/fold · 71 tokens

integration-test-author

Writes and extends fold's integration tests using real MCP SDK peers behind the gateway. Use when a change needs test coverage — new gateway behavior, reload/discovery paths, policy or auth changes, or a repro for a reported bug.

fold-run/fold · 50 tokens