Borrowing it
Nothing to install: this file belongs to hara-lang/hara-mcp. 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/hara-lang/hara-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/hara-lang/hara-mcpWrote 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/hara-lang/hara-mcp/agents-md)<a href="https://agentmods.dev/instructions/hara-lang/hara-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/hara-lang/hara-mcp/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.1 | $0.00550 | $0.00550 |
| Opus 5 | $0.00275 | $0.00275 |
| Sonnet 5 | $0.00110 | $0.00110 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
hara-mcp 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 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent instructions
Scope
This repository owns the MCP gateway, host registry, routing, temporary source/result projection, and protocol adapters for Hara execution hosts. It does not own Hara evaluation semantics, Chrome/browser capabilities, Greenways application records, or a second Sandbox/LiveSession implementation.
Required boundaries
- Keep the public pure catalogue limited to
hara_runtime_get,hara_eval,hara_call, andhara_checkuntil its owning issue changes. - A pure tool must never enable browser, network, persistent filesystem, package, process, database, shell, provider, or external-effect authority through options.
- Never pass MCP bearer credentials to an execution host or device credentials to an MCP client.
- Keep the Phase 1 relay bound exactly to
127.0.0.1. Do not add wildcard, LAN, public, or implicit bind modes. - Treat the loopback bearer token as transport-only authority. Never place it in descriptors, Hara requests, results, MCP output, diagnostics, or logs.
- Relay commands are redelivered until acknowledged. Preserve stable command IDs and require host-side request de-duplication rather than weakening delivery to best-effort at-most-once behavior.
- Never silently fall back to a test fixture, hosted evaluator, broader host profile, or trusted local runtime.
- Treat
hara.execution-host/0-alphaandhara.mcp-pure/0-alphaas Hara-owned contracts. Provisional copies in this repository must be replaced by generated or pinned upstream contracts under issue #3. - The deterministic fixture is transport test evidence only. It must remain disabled by default and identify itself as
test-fixture. - Qualified calls invoke an already-loaded Var with transfer-safe arguments. Do not construct call source by concatenating arguments.
- Unknown fields, versions, profiles, capabilities, command acknowledgements, generations, and lifecycle transitions fail closed.
- Request cancellation must flow from
context.mcpReq.signalthrough the gateway to the selected host. Do not replace cancellation with a fabricated successful terminal result.
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 · 41 lines · 550 tokens per session scan A 71d97d554ca9
hara-mcp AGENTS.md is an instructions file published in the GitHub repository hara-lang/hara-mcp (0 stars, last pushed 14d ago), licensed Apache-2.0. It adds 550 tokens to every session, about $0.0028 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
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).
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.
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.
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).
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.