CONTRIBUTING

A contribution guide for adding or improving skills in the Agent Maxxing collection. It explains where different kinds of skills belong, how to test them, and what to include when sharing changes.

In plain words
What is it for?
Use it when creating a new skill, improving an existing one, adding workflow examples, or preparing a contribution for review.
Why use it?
Without shared contribution rules, new skills can be hard to find, inconsistent, or difficult to review. The guide gives contributors a common structure and submission process.

Skill for Claude CodeCodex

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 skills/subhansh-dev/agent-maxxing/contributing
Any agent
npx skills add subhansh-dev/agent-maxxing --skill contributing
Clone the repo
git clone --depth 1 https://github.com/subhansh-dev/agent-maxxing

Made for: Claude Code, Codex.

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 742 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.00742
Opus 5 $0.00000 $0.00371
Sonnet 5 $0.00000 $0.00148
Haiku 4.5 $0.00000 $0.00074

Measured 2d ago against content hash 0794fa027af2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

CONTRIBUTING 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 2d ago.

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.

CONTRIBUTING/SKILL.md · 134 lines

How it starts

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

Contributing to Agent Maxxing

Thanks for considering contributing! Here's how to add skills, improve existing ones, or share workflow examples.

How to Contribute

1. Add a New Skill

  1. Fork the repository
  2. Choose the appropriate folder:
    • frontend-design/ — UI, CSS, motion, typography
    • engineering/ — Code, security, testing, debugging
    • content/ — Writing, humanization
    • visual/ — Diagrams, memes, canvas
    • agent-meta/ — Self-improvement, skill creation
    • workflows/ — Task management, git, orchestration
    • adaptation/ — Cross-platform, responsive
    • components/ — Reusable UI patterns
    • system-prompts/ — Extracted from top AI agents
  3. Create your skill file following the template below
  4. Test with Claude Code, Codex, or any compatible agent
  5. Submit a Pull Request

2. Improve Existing Skills

  • Add real-world examples and use cases
  • Enhance with modern patterns
  • Fix typos, improve clarity
  • Add success metrics

3. Share Workflow Examples

Used these skills successfully? Add an example to examples/:

  • Describe the scenario
  • List the skills you used
  • Show the step-by-step workflow
  • Include the outcome

4. Report Issues

  • Check if the issue already exists
  • Provide clear reproduction steps
  • Include context about your use case

Skill File Structure

Every skill should follow this structure:

---
name: skill-name
description: One-line description of what this skill does
---

# Skill Name

## When to Use
- Trigger condition 1
- Trigger condition 2
- "Do X when Y" pattern

## Instructions

### Phase 1: [Name]
1. Step one
2. Step two

### Phase 2: [Name]
1. Step one
2. Step two

## Rules
- Rule 1
- Rule 2

## Examples

### Example 1: [Scenario]
[Concrete example of the skill in action]

### Example 2: [Scenario]
[Another concrete example]

## Output Format

```json
{
  "field": "description"
}

## Style Guide

### Writing
- Write like you're talking to a smart friend
- Be direct, opinionated, specific
- Avoid AI slop words (delve, tapestry, crucial, pivotal)
- Use active voice
- Vary sentence rhythm

Read the full file on GitHub · 134 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. 2d ago First seen · 134 lines · 0 tokens per session scan A 0794fa027af2

Subscribe to this mod's changes

CONTRIBUTING is a skill published in the GitHub repository subhansh-dev/agent-maxxing (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 742 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-31.