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.
git clone --depth 1 https://github.com/majorelalexis-stack/maxiaWrote 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/commands/majorelalexis-stack/maxia/maxia-awp)<a href="https://agentmods.dev/commands/majorelalexis-stack/maxia/maxia-awp"><img src="https://agentmods.dev/badge/commands/majorelalexis-stack/maxia/maxia-awp.svg" alt="Measured on agentmods" 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.00021 | $0.00293 |
| Opus 5 | $0.00010 | $0.00147 |
| Sonnet 5 | $0.00004 | $0.00059 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
maxia-awp 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 7d 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.
What it actually says
AWP (Autonomous Worker Protocol) integration on MAXIA.
If action is 'info' or empty:
- Call
GET https://maxiaworld.app/api/awp/info - Display: protocol info, registered agents, total staked, features
If action is 'discover':
- Call
GET https://maxiaworld.app/api/awp/discover - Display: agent name, capabilities, trust score, total staked
If action is 'leaderboard':
- Call
GET https://maxiaworld.app/api/awp/leaderboard - Display: rank, agent, staked amount, trust score
To register/stake:
- Register:
POST /api/awp/registerwith{agent_name, wallet_address, capabilities} - Stake:
POST /api/awp/stakewith{amount_usdc, lock_period_days} - APY: 3% (30d), 5% (90d), 8% (180d), 12% (365d)
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.
- 7d ago First seen · 28 lines · 21 tokens per session scan A 56b24230d2a0
maxia-awp is a command published in the GitHub repository majorelalexis-stack/maxia (0 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 293 once invoked, about $0.0001 per session on Opus 5. 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 commands, from other repositories
deploy
Deploy Solana program (devnet first, then mainnet).
invariant
Generate Foundry invariant tests for property-based fuzzing. The high-value command for serious teams.
audit-strict
Multi-pass consensus audit — runs the audit twice with different prompts, only reports consensus findings. Aggressively cuts false positives.
docs-remove
Remove a user-defined source alias from sources.yaml, optionally deleting its cached Markdown.
analyze
Conduct a full gas optimization analysis on a Foundry Solidity project.
checklist
Generate a custom checklist for the current feature based on user requirements.