Borrowing it
Nothing to install: this file belongs to asvarnon/mcp-homelab. 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/asvarnon/mcp-homelab/master/.github/instructions/agent-workflow.instructions.mdgit clone --depth 1 https://github.com/asvarnon/mcp-homelabWrote 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/asvarnon/mcp-homelab/agent-workflow)<a href="https://agentmods.dev/instructions/asvarnon/mcp-homelab/agent-workflow"><img src="https://agentmods.dev/badge/instructions/asvarnon/mcp-homelab/agent-workflow/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/asvarnon/mcp-homelab/agent-workflow"><img src="https://agentmods.dev/badge/instructions/asvarnon/mcp-homelab/agent-workflow.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.00513 | $0.00513 |
| Opus 5.5 | $0.00205 | $0.00205 |
| Sonnet 5.5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
mcp-homelab agent-workflow.instructions.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 1mo 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Workflow Instructions
These rules apply to every interaction in this workspace. They are non-negotiable and override default agent behavior.
Session Start (do this before anything else)
- Run
memory view /memories/session/to list session files - Read the most recent session file relevant to the current task before taking any action
- Read
/memories/repo/versioning.mdbefore any release, deployment, or version-related work - Only then proceed with the user's request
Session Notes (during the session)
- Write to
/memories/session/after each significant action — not at the end - Use one rolling file per topic/task (e.g.,
session-v1.5.0.md,dhcp-backend.md) - Record: decisions made, files modified, commands run, open questions, pending steps
- If a session file for the current topic already exists, update it — don't create a duplicate
Promote Findings Immediately
- When something permanent is discovered (a correct process, a wrong assumption, a repo convention), write it to
/memories/repo/or/memories/user-preferences.mdimmediately — not at end of session - Do not rely on session compaction to preserve important facts
Release / Publish Checklist
Before any PyPI publish, package build, or version tag operation:
- Check
.github/workflows/for an existing release workflow - If a workflow exists: push a
vX.Y.Ztag — the workflow handles everything - NEVER run
twine uploadorpython -m build+ upload directly — this bypasses Trusted Publishing and triggers a PyPI security warning - The publish workflow (
publish-release.yml) hasskip-existing: true— re-tagging is safe
Code Authorship
- NEVER write or edit Python code directly — always delegate to Codex Agent via
runSubagent - This includes: new files, edits to existing Python files, test files, config changes in Python projects
- Orchestrator role only: plan, scope, review, validate tests, manage git
Git Workflow
- Feature/fix branches only → PR → merge
- NEVER push directly to master — no exceptions, even for "just a config file"
- CI workflow (
publish-release.yml) uses branch protection — direct pushes will warn
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.
- 1mo ago First seen · 48 lines · 513 tokens per session scan A 9b26d2a1f70b
mcp-homelab agent-workflow.instructions.md is an instructions file published in the GitHub repository asvarnon/mcp-homelab (2 stars, last pushed 4mo ago), licensed MIT. It adds 513 tokens to every session, about $0.0021 per session on Opus 5.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
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
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.