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 instructions/bofai/mcp-server-tron/agents-mdgit clone --depth 1 https://github.com/BofAI/mcp-server-tronWrote 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/instructions/bofai/mcp-server-tron/agents-md)<a href="https://agentmods.dev/instructions/bofai/mcp-server-tron/agents-md"><img src="https://agentmods.dev/badge/instructions/bofai/mcp-server-tron/agents-md.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 | $0.01354 | $0.01354 |
| Opus 5 | $0.00677 | $0.00677 |
| Sonnet 5 | $0.00271 | $0.00271 |
| Haiku 4.5 | $0.00135 | $0.00135 |
Grade C, and why
mcp-server-tron AGENTS.md scanned grade C with 1 finding 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 5d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- **Clean**: `rm -rf build` How it starts
The opening of the file, as written. The whole thing β 128 lines β stays where its author put it; the contents beside it link to each section on GitHub.
Agent Guidelines: MCP Server Tron
This document provides essential information for AI agents working on this repository.
π Commands
Development & Build
- Build:
npm run build(runstsc) - Lint:
npm run lint(runseslint) - Fix Lint:
npm run lint:fix - Clean:
rm -rf build
Testing
- Run all tests:
npm test(runsvitest run) - Run specific test file:
npx vitest tests/core/services/utils.test.ts - Run with UI:
npx vitest --ui - Watch mode:
npx vitest
Execution
- Start (Stdio):
npm start(usestsxto runsrc/index.ts) - Start (HTTP):
npm run start:http - Read-only mode: Add
--readonlyor-rto disable write tools (e.g.,npm start -- --readonly) - Inspect:
npm run inspect(launches MCP Inspector)
π¨ Code Style & Conventions
π¦ Imports
- Use ES Modules (
import/export). - When importing from local files, follow
NodeNextresolution: use.jsextension in the import path (e.g.,import { foo } from "./foo.js"). - Organize imports: built-ins first, then external libraries, then internal modules.
π· Naming Conventions
- Files:
kebab-case.ts(e.g.,http-server.ts). - Tests:
name.test.tsorname_integration.ts. - Variables/Functions:
camelCase. - Classes/Interfaces:
PascalCase. - MCP Tools:
snake_case(e.g.,get_wallet_address). - Constants:
UPPER_SNAKE_CASE.
π Architecture
- src/core/services: Contains the business logic and TronWeb integrations.
- src/core/tools/: MCP tool definitions split by category (wallet, network, address, block, balance, transaction, contract, transfer, staking, account), with schema validation using
zod. - src/core/prompts.ts: MCP prompt definitions.
- src/server: Protocol-specific server implementations (Stdio/HTTP).
π¦ Error Handling
- Services: Throw descriptive
Errorobjects. - Tools: Use
try-catchblocks. ReturnisError: trueand a structured error message in thecontentarray if an operation fails. - Avoid
process.exit()in library code; let the server handle fatal errors.
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.
- 5d ago First seen Β· 128 lines Β· 1,354 tokens per session scan C 713d6a157def
mcp-server-tron AGENTS.md is an instructions file published in the GitHub repository BofAI/mcp-server-tron (18 stars, last pushed 5mo ago), licensed MIT. It adds 1,354 tokens to every session, about $0.0068 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart β add a new integration in 5 steps, integration architecture and integrationmanifest β file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.