Borrowing it
Nothing to install: this file belongs to rockexe0000/my-awesome-copilot. 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/rockexe0000/my-awesome-copilot/main/.github/instructions/copilot-thought-logging.instructions.mdgit clone --depth 1 https://github.com/rockexe0000/my-awesome-copilotWrote 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/rockexe0000/my-awesome-copilot/copilot-thought-logging)<a href="https://agentmods.dev/instructions/rockexe0000/my-awesome-copilot/copilot-thought-logging"><img src="https://agentmods.dev/badge/instructions/rockexe0000/my-awesome-copilot/copilot-thought-logging/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/rockexe0000/my-awesome-copilot/copilot-thought-logging"><img src="https://agentmods.dev/badge/instructions/rockexe0000/my-awesome-copilot/copilot-thought-logging.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.00690 | $0.00690 |
| Opus 5 | $0.00345 | $0.00345 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
my-awesome-copilot copilot-thought-logging.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 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.
This is a copy
100% identical to custom_github_copilot_agent_builder copilot-thought-logging.instructions.md — 1 line 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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Process tracking Instructions
ABSOLUTE MANDATORY RULES:
- You must review these instructions in full before executing any steps to understand the full instructions guidelines.
- You must follow these instructions exactly as specified without deviation.
- Do not keep repeating status updates while processing or explanations unless explicitly required. This is bad and will flood Copilot session context.
- NO phase announcements (no "# Phase X" headers in output)
- Phases must be executed one at a time and in the exact order specified.
- NO combining of phases in one response
- NO skipping of phases
- NO verbose explanations or commentary
- Only output the exact text specified in phase instructions
Phase 1: Initialization
- Create file
\Copilot-Processing.mdin workspace root - Populate
\Copilot-Processing.mdwith user request details - Work silently without announcements until complete.
- When this phase is complete keep mental note of this that <Phase 1> is done and does not need to be repeated.
Phase 2: Planning
- Generate an action plan into the
\Copilot-Processing.mdfile. - Generate detailed and granular task specific action items to be used for tracking each action plan item with todo/complete status in the file
\Copilot-Processing.md. - This should include:
- Specific tasks for each action item in the action plan as a phase.
- Clear descriptions of what needs to be done
- Any dependencies or prerequisites for each task
- Ensure tasks are granular enough to be executed one at a time
- Work silently without announcements until complete.
- When this phase is complete keep mental note of this that <Phase 2> is done and does not need to be repeated.
Phase 3: Execution
- Execute action items from the action plan in logical groupings/phases
- Work silently without announcements until complete.
- Update file
\Copilot-Processing.mdand mark the action item(s) as complete in the tracking. - When a phase is complete keep mental note of this that the specific phase from
\Copilot-Processing.mdis done and does not need to be repeated. - Repeat this pattern until all action items are complete
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 · 62 lines · 690 tokens per session scan A ecd2ee585500
my-awesome-copilot copilot-thought-logging.instructions.md is an instructions file published in the GitHub repository rockexe0000/my-awesome-copilot (1 stars, last pushed 8mo ago), licensed MIT. It adds 690 tokens to every session, about $0.0034 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to custom_github_copilot_agent_builder copilot-thought-logging.instructions.md, differing in 1 line, and is treated as a copy.
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.