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 agentmods add skills/mangrovetechnologies/mangrove-agent/check-alignmentnpx skills add MangroveTechnologies/mangrove-agent --skill check-alignmentgit clone --depth 1 https://github.com/MangroveTechnologies/mangrove-agentWrote 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/mangrovetechnologies/mangrove-agent/check-alignment)<a href="https://agentmods.dev/skills/mangrovetechnologies/mangrove-agent/check-alignment"><img src="https://agentmods.dev/badge/skills/mangrovetechnologies/mangrove-agent/check-alignment.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.00088 | $0.00865 |
| Opus 5 | $0.00044 | $0.00432 |
| Sonnet 5 | $0.00018 | $0.00173 |
| Haiku 4.5 | $0.00009 | $0.00086 |
Grade A, and why
check-alignment 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 6d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Alignment
Parse $ARGUMENTS as a natural-language description of a proposed change — could be a new feature, a refactor, a dependency change, a workflow tweak.
Review the proposal against each of these documents. For every one that exists, state whether the proposal aligns or conflicts. If it conflicts, cite the specific principle or decision it violates and suggest a concrete adjustment.
Documents to check
1. CLAUDE.md — project identity + persona
- "What This Is" section: does the proposal still describe a local trading bot? Any scope drift toward cloud / hosted / multi-tenant breaks the v1 framing.
- "Architecture" section: dual-protocol (REST + MCP), three-tier access (free / auth / x402), service-layer pattern. Does the proposal respect these layers, or does it duplicate logic?
- "Project Context" + "Agent Identity": does the proposal change Tim's persona or the Sage agent? Flag if yes — persona is set in
CLAUDE.mdand changes there are explicit, deliberate edits, not side effects of feature work.
2. .claude/rules/trading-bot-workflow.md — the 9 operating principles
Check each principle if relevant:
- Strategy-first, always (no manual-swap-by-default)
- Bulk candidate evaluation (no label-pick)
- Every recommendation cites Mangrove intelligence
- Paper before live
- Explicit confirmation at status transitions
- Small first allocation
- Wallet secrets NEVER in chat
- Signing is 1inch-only (hard guard at
wallet_manager._validate_sign_target) - Testnet-first for learning (Base Sepolia 84532 by default)
Plus the stage machine (Stage 0 tour → 1 Orient → 2 Author → 3 Review → 4 Paper → 4.5 Wallet → 5 Live → 6 Monitor). Does the change preserve the stage boundaries?
3. .claude/rules/wallet-presentation.md — wallet handling
- Never echo plaintext keys / vault_tokens in chat prose.
- Default to testnet for new wallets.
- All signing routes through
wallet_manager.sign()which is hard-guarded to 1inch-only payloads. - The signing guard allowlist (
_ONEINCH_ROUTERS) must only be expanded with explicit review.
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.
- 6d ago First seen · 73 lines · 88 tokens per session scan A fee1937bbe92
check-alignment is a skill published in the GitHub repository MangroveTechnologies/mangrove-agent (5 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 865 once invoked, about $0.0004 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 skills, from other repositories
sui-publish
Publishing, upgrading, and deploying Sui Move packages. Use this skill when the user needs to publish a package, upgrade a published package, deploy to multiple networks, serialize transactions for multisig signing, run a local Sui network (localnet), prepare for Mainnet launch, monitor production deployments, or…
t2000-job
Escrow USDC for agent-to-agent deliverable work (A2A jobs). Use when hiring another agent for async work (research reports, builds, SLA tasks) or when selling deliverable work yourself (list a service: fixed price + SLA, no server needed), or posting/claiming open jobs on the board (t2 job open / claim) — anything…
t2000-engineering
The deep version of the t2000 engineering discipline — trace-the-full-path debugging, verifiable success criteria, simplicity/surgical-change rules, complete-removal (no orphans), and the Musk product algorithm. CLAUDE.md carries the one-line assertions; read this for the worked examples, the ask-vs-proceed test, the…
move-unit-testing
Use when writing unit tests for Move smart contracts on Sui. Applies to test function naming, assertions, test attributes, context usage, and cleanup patterns. Use whenever user asks to write tests, add tests, or test a Move module.
sui-object-model
Deep reference for the Sui object model: ownership types, object abilities, dynamic fields, collections, versioning, transfer patterns, and derived objects. Use this skill whenever the user asks about Sui objects, object ownership (address-owned, shared, immutable, wrapped), how to transfer or share or freeze objects…
t2000-setup
Set up a t2000 terminal Agent Wallet (t2 init) when the user needs a local CLI key file — not for Claude-only marketplace (that is Passport Connect OAuth only). Also use when they say "set up t2000", "install the wallet", or "connect t2000 to Claude / Cursor" if a local wallet is in scope. Covers npm CLI install…