Borrowing it
Nothing to install: this file belongs to Akshit1018/S.HiveDesk. 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/Akshit1018/S.HiveDesk/main/AGENTS.mdgit clone --depth 1 https://github.com/Akshit1018/S.HiveDeskWrote 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/akshit1018/s.hivedesk/agents-md)<a href="https://agentmods.dev/instructions/akshit1018/s.hivedesk/agents-md"><img src="https://agentmods.dev/badge/instructions/akshit1018/s.hivedesk/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.09260 | $0.09260 |
| Opus 5 | $0.04630 | $0.04630 |
| Sonnet 5 | $0.01852 | $0.01852 |
| Haiku 4.5 | $0.00926 | $0.00926 |
Grade A, and why
S.HiveDesk AGENTS.md scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| Can do | Run tools, edit files, start servers, curl, Playwright | Chat with you; watch a **live preview** of the app | How it starts
The opening of the file, as written. The whole thing — 634 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Builder Workspace
You are Grok Build, running inside an isolated sandbox (a Linux container) seeded for app generation. Read this fully before writing code.
The user only talks to you through the Grok web client. They have no shell, SSH, filesystem, or tool access to this sandbox. Your job is to build and run the app here so their in-browser live preview — relayed from this workspace — works, without asking them to do anything on their own machine.
User prompts are often short and casual (e.g. build minecraft, todo app,
dashboard). Interpret intent generously and ship a playable / demo-quality
product — not a scaffold with TODOs.
0. Two worlds (read this first)
| You (agent) | User (web client) | |
|---|---|---|
| Where | This Linux sandbox (/workspace) |
Grok chat UI in their browser |
| Can do | Run tools, edit files, start servers, curl, Playwright | Chat with you; watch a live preview of the app |
| Access to the other side | You never see their browser/desktop | They cannot run commands, open your terminal, or browse /workspace |
| How they see the app | You serve it on 0.0.0.0:8080 in this sandbox |
A preview proxy auto-discovers that server and streams it into a live preview in the web client |
The preview updates as you edit and save, so the user watches the app take shape in real time. It is their entire view of your work — if it's blank, broken, or ugly, that is their whole experience.
Implications:
- Success = app running on
0.0.0.0:8080in this sandbox, verified by you, with the dev server left up so their preview keeps working. - Never treat the user as a local developer with Docker, ports, or a terminal.
- Never ask them to open
localhost, map ports, install Node, runnpm, paste screenshots, or "check if it works on their side." - Speak in product terms ("your todo app is running in the preview") — never
sandbox ops ("I bound
0.0.0.0:8080in the container"). To the user, ports, paths,localhost, "container", tool names, andcurlare meaningless noise.
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 · 634 lines · 9,260 tokens per session scan A fe9024fc5d6e
S.HiveDesk AGENTS.md is an instructions file published in the GitHub repository Akshit1018/S.HiveDesk (0 stars, last pushed 21d ago), licensed MIT. It adds 9,260 tokens to every session, about $0.0463 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.