Contributor Guidelines
Last updated: April 2026 · These guidelines apply to all agents submitted to the public marketplace.
1. What makes a great agent?
The best agents on AgentHut are specific, actionable, and immediately useful. Before you submit, ask yourself: could a developer or business user copy this into Cursor or ChatGPT and get value within 5 minutes?
- Specific scope — narrow is better. “Write Pytest unit tests for a FastAPI route” beats “write Python tests”.
- Clear instructions — describe what the agent does in the first 2–3 lines of the file.
- Real examples — include at least one worked example or sample input/output.
- Up-to-date — reference current tool versions where relevant (e.g. “Cursor 1.x”, “GPT-4o”).
2. File format requirements
# Agent Title
## Purpose
One sentence summary.
## Instructions
Step-by-step or freeform prompt instructions.
## Example
Input → Output example.
- Files must be
.md(Markdown) format, maximum 5 MB - ZIP packages may include supporting files (templates, schemas) up to 10 MB — Pro only
- No binary executables, scripts, or code that runs outside of an AI context window
- UTF-8 encoding required
3. Metadata best practices
- Title — concise, searchable, ≤60 characters. Use plain English, not CamelCase.
- Tagline — one sentence describing the outcome. Start with a verb: “Generate…”, “Refactor…”, “Analyse…”.
- Category — pick the most specific category available. Miscategorised agents rank lower.
- Tags — add 3–8 tags using common search terms. Include the tool name (cursor, copilot, chatgpt) if relevant.
- Runtime targets — select every AI tool the agent is compatible with.
4. Content standards
All submitted agents must:
- Be original work or properly licensed content you have rights to distribute
- Not contain harmful, deceptive, or illegal instructions
- Not be designed to exploit, circumvent, or manipulate AI safety filters
- Not collect, exfiltrate, or misuse user data
- Not infringe on third-party intellectual property
Agents that violate these standards will be rejected and repeat violations may result in account suspension. See the full Contributor Requirements in our Terms.
5. The review process
- S
Submit
Once you click Publish, your agent enters Pending status. You can only have one agent under review at a time.
- R
Review
Our admin team reviews the agent within 2–5 business days for quality, safety, and formatting.
- F
Feedback or Live
If changes are needed, you'll receive specific feedback. If approved, the agent goes Live on the marketplace.
- U
Updates
Versioned updates to live agents go through a lighter review. Your download stats are preserved across versions.
6. Premium agents & earnings
- Once your agent reaches 100 unique downloads, you can enable premium pricing (if you set a price).
- Premium prices must be between $0.99 and $499.99.
- You earn the contributor share of each sale (about 70% by default) — AgentHut retains the platform fee portion; exact splits are admin-configurable — see Terms.
- Payouts are processed via Stripe Connect. You must complete Connect onboarding to receive payments.
- A minimum balance of $10 is required before a payout is initiated.
7. Tips for getting discovered
- Use search keywords in your title and tagline that developers actually type
- Add a short description with a concrete use-case example
- Share your agent page link on Reddit, Twitter/X, or Discord communities
- Keep agents updated — stale agents rank lower over time
- Respond to comments — engagement signals quality to our ranking algorithm
8. Questions?
Reach the creator support team at creators@agenthut.ai. We typically respond within one business day.