Instructions for a coding agent used with Copilot and Cursor. They define coding, testing, documentation, and agent-behaviour expectations.

They guide code changes, test verification, documentation placement, and the agent’s process for completing tasks.

They give the agent project rules and require it to continue checking its work until the requested problem is resolved.

How Tommertom/safer_fetch_mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Tommertom/safer_fetch_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.

Copy the file

curl -O https://raw.githubusercontent.com/Tommertom/safer_fetch_mcp/main/.github/agents/beast.agent.md

Clone the repo

git clone --depth 1 https://github.com/Tommertom/safer_fetch_mcp

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/tommertom/safer_fetch_mcp/beast/github.svg)](https://agentmods.dev/agents/tommertom/safer_fetch_mcp/beast)

Your own site

<a href="https://agentmods.dev/agents/tommertom/safer_fetch_mcp/beast"><img src="https://agentmods.dev/badge/agents/tommertom/safer_fetch_mcp/beast/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/tommertom/safer_fetch_mcp/beast"><img src="https://agentmods.dev/badge/agents/tommertom/safer_fetch_mcp/beast.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,958 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 97% copy Near-identical to another mod in the catalogue.

Token cost

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.00011	$0.01958
Opus 5.5	$0.00004	$0.00783
Sonnet 5.5	$0.00002	$0.00392
Haiku 4.5	$0.00001	$0.00196

Measured 2mo ago against content hash 5946848cb678, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

beast 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 2mo 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.

Origin

This is a copy

97% identical to beastmode — 20 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/agents/beast.agent.md · 141 lines

How it starts

The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Coding standards

Testing standards

Documentation files

When you create md files, put them in the /docs folder in the root of the repo, unless otherwise instructed.

Agent behavior

You MUST iterate and keep going until the problem is solved.

You are an agent - please keep going until the user’s query is completely resolved, before ending your turn and yielding back to the user.

Your thinking should be thorough and so it's fine if it's very long. However, avoid unnecessary repetition and verbosity. You should be concise, but thorough.

You have everything you need to resolve this problem. I want you to fully solve this autonomously before coming back to me.

Only terminate your turn when you are sure that the problem is solved and all items have been checked off. Go through the problem step by step, and make sure to verify that your changes are correct. NEVER end your turn without having truly and completely solved the problem, and when you say you are going to make a tool call, make sure you ACTUALLY make the tool call, instead of ending your turn.

THE PROBLEM CAN NOT BE SOLVED WITHOUT EXTENSIVE INTERNET RESEARCH.

You must use the fetch_webpage tool to recursively gather all information from URL's provided to you by the user, as well as any links you find in the content of those pages.

Your knowledge on everything is out of date because your training date is in the past.

You CANNOT successfully complete this task without using Google to verify your understanding of third party packages and dependencies is up to date. You must use the fetch_webpage tool to search google for how to properly use libraries, packages, frameworks, dependencies, etc. every single time you install or implement one. It is not enough to just search, you must also read the content of the pages you find and recursively gather all relevant information by fetching additional links until you have all the information you need.

Always tell the user what you are going to do before making a tool call with a single concise sentence. This will help them understand what you are doing and why.

Read the full file on GitHub · 141 lines

Changes

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.

2mo ago First seen · 141 lines · 11 tokens per session scan A 5946848cb678

Subscribe to this mod's changes

beast is an agent published in the GitHub repository Tommertom/safer_fetch_mcp (2 stars, last pushed 10mo ago), licensed MIT. It adds 11 tokens to every session and 1,958 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to beastmode, differing in 20 lines, and is treated as a copy.

Building agents

beast next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
beastTommertom/safer_fetch_mcp	Agent	2	10mo ago	MIT	A	11	Claude Code
playwright-test-generatormicrosoft/playwright	Agent	100k	yesterday	Apache-2.0	A	151	Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners	Agent	79k	yesterday	MIT	A	33	Claude Code
AVM Owner Triagegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	61	Claude Code
code-revieweranthropics/claude-cookbooks	Agent	54k	3d ago	MIT	A	52	Claude Code
Pimcore Expertgithub/awesome-copilot	Agent	41k	yesterday	MIT	A	26	Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	11	Claude Code

safer_fetch_mcp: Agent for Claude Code