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.
npx skills add subhansh-dev/agent-maxxing --skill contributinggit clone --depth 1 https://github.com/subhansh-dev/agent-maxxingWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/subhansh-dev/agent-maxxing/contributing)<a href="https://agentmods.dev/skills/subhansh-dev/agent-maxxing/contributing"><img src="https://agentmods.dev/badge/skills/subhansh-dev/agent-maxxing/contributing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/subhansh-dev/agent-maxxing/contributing"><img src="https://agentmods.dev/badge/skills/subhansh-dev/agent-maxxing/contributing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00742 |
| Opus 5.5 | $0.00000 | $0.00297 |
| Sonnet 5.5 | $0.00000 | $0.00148 |
| Haiku 4.5 | $0.00000 | $0.00074 |
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 1mo 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.
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
- Fork the repository
- Choose the appropriate folder:
frontend-design/— UI, CSS, motion, typographyengineering/— Code, security, testing, debuggingcontent/— Writing, humanizationvisual/— Diagrams, memes, canvasagent-meta/— Self-improvement, skill creationworkflows/— Task management, git, orchestrationadaptation/— Cross-platform, responsivecomponents/— Reusable UI patternssystem-prompts/— Extracted from top AI agents
- Create your skill file following the template below
- Test with Claude Code, Codex, or any compatible agent
- 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
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.
- 1mo ago First seen · 134 lines · 0 tokens per session scan A 0794fa027af2
CONTRIBUTING is a skill published in the GitHub repository subhansh-dev/agent-maxxing (2 stars, last pushed 3mo 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.
Other skills, from other repositories
batch-api
Prepare a many-file, single-turn transform (translate, rewrite, extract) as a plan and submit it to the asynchronous, half-price DashScope Batch API; results are delivered as new files hours later. Invoke explicitly with /batch-api.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
pr-description-writer
Redacta una descripción de pull request clara y estructurada a partir de un diff de git, resumen de rama o lista de commits. Úsalo cuando te pidan escribir una descripción de PR, redactar una solicitud de cambios o documentar cambios de código. Produce una descripción con resumen, motivación, cambios realizados, pasos…