Borrowing it
Nothing to install: this file belongs to MiHashport/MiHashport-Backend. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MiHashport/MiHashport-Backend/main/AGENTS.mdgit clone --depth 1 https://github.com/MiHashport/MiHashport-BackendWrote 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/mihashport/mihashport-backend/agents-md)<a href="https://agentmods.dev/instructions/mihashport/mihashport-backend/agents-md"><img src="https://agentmods.dev/badge/instructions/mihashport/mihashport-backend/agents-md/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/instructions/mihashport/mihashport-backend/agents-md"><img src="https://agentmods.dev/badge/instructions/mihashport/mihashport-backend/agents-md.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.00667 | $0.00667 |
| Opus 5 | $0.00333 | $0.00333 |
| Sonnet 5 | $0.00133 | $0.00133 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
MiHashport-Backend AGENTS.md 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 9d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Instructions for AI coding agents contributing to this repository.
Repo context
- Stack: NestJS 11, TypeScript (strict mode), TypeORM + PostgreSQL,
@stellar/stellar-sdk(Horizon + Soroban RPC), Jest. - Build:
npm installthennpm run build. - Run (dev):
npm run start:dev(requires a.env— copy.env.example). - Test:
npm run test(unit tests, Jest, colocated as*.spec.ts). - Lint/format:
npm run lint,npm run format. - Key directories:
src/modules/<domain>/— one folder per domain (users,wallet,stellar,contracts,whatsapp,health), each with its own module, controller, service,dto/, andentities/.src/config/— typed, Joi-validated configuration (ConfigModule).src/database/— TypeORM data source and migrations.src/common/— global filters/interceptors.docs/PLAN.md— the phased roadmap; issues are derived from it.
Rules for contributions
- Address each issue in its own commit.
- The PR description must include
Closes #<issue>for every issue the PR addresses. - Commit messages must be single-line only (no multi-paragraph bodies).
- Do not add a
Co-authored-byline to commits. - Keep the implementation minimal and focused on the issue at hand — do not bundle unrelated fixes or refactors into the same PR.
- Read the surrounding code in the domain folder you're touching before writing anything; integrate with the existing module/controller/service/DTO structure rather than introducing a new pattern.
- Avoid over-engineering. Don't build abstractions, config options, or error
handling for cases the issue doesn't require, and don't assume unfinished
parts of the codebase (e.g. stubbed services that throw
NotImplementedException) are stable — check before building on top of them. - This project is under active development: expect bugs, missing pieces, and incomplete implementations elsewhere in the codebase. Do not "fix" things outside your issue's scope, even if you spot something wrong — file a new issue instead.
- The test suite may or may not be reliable at any given time. If tests exist and run, use them to validate your change. If they don't cover your change, don't assume passing behavior — prioritize clean, correct, minimal code either way, and add a test if one is missing for the code you touched.
- Keep the scope as small as possible while still fully addressing each issue.
- Do not commit or push any implementation notes, plan files, or scratch
markdown (e.g.
IMPLEMENTATION.md,NOTES.md,TODO.md,*.plan.md). Keep these local only — they're covered by.gitignore, but double-check before committing.
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.
- 9d ago First seen · 53 lines · 667 tokens per session scan A a1d3d8d786c4
MiHashport-Backend AGENTS.md is an instructions file published in the GitHub repository MiHashport/MiHashport-Backend (2 stars, last pushed 2mo ago), licensed MIT. It adds 667 tokens to every session, about $0.0033 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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 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).
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.