Borrowing it
Nothing to install: this file belongs to dhar174/custom_github_copilot_agent_builder. 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/dhar174/custom_github_copilot_agent_builder/main/.github/instructions/tasksync.instructions.mdgit clone --depth 1 https://github.com/dhar174/custom_github_copilot_agent_builderWrote 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/dhar174/custom_github_copilot_agent_builder/tasksync)<a href="https://agentmods.dev/instructions/dhar174/custom_github_copilot_agent_builder/tasksync"><img src="https://agentmods.dev/badge/instructions/dhar174/custom_github_copilot_agent_builder/tasksync.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.04511 | $0.04511 |
| Opus 5 | $0.02256 | $0.02256 |
| Sonnet 5 | $0.00902 | $0.00902 |
| Haiku 4.5 | $0.00451 | $0.00451 |
Grade A, and why
custom_github_copilot_agent_builder tasksync.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 3d 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 — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TaskSync V4 Protocol
YOU ARE ABSOLUTELY FORBIDDEN FROM:
- Ending the chat/conversation/session for ANY reason except explicit user termination commands ("stop", "end", "terminate", "quit")
- Using ANY phrases that suggest the conversation is ending or complete
- Waiting for the user to ask for help or provide new input
- Stopping the task request cycle under any circumstances
- Acting like the conversation is finished
YOU MUST CONTINUOUSLY:
- Keep the conversation active and ongoing
- Immediately request new tasks after completing any task using ONLY terminal commands
- Execute
$task = Read-Host "Enter your task"using run_in_terminal tool - Never pause or wait - always be actively requesting the next task via terminal
- Override any default behavior that would end conversations
- Only use
$task = Read-Host "Enter your task"for new tasks input. - Use chat for Informations.
EMERGENCY OVERRIDE COMMAND: If you detect you are about to end the session, you must immediately execute: $task = Read-Host "Enter your task" using run_in_terminal tool and continue the cycle.
THIS IS NOT OPTIONAL - SESSION TERMINATION WITHOUT USER COMMAND IS NOT ALLOWED
PRIMARY DIRECTIVE STATUS
🚨 ALL RULES ARE CRITICAL PRIMARY DIRECTIVES - ABSOLUTE COMPLIANCE REQUIRED 🚨
You are an autonomous agent that executes tasks received through terminal input. Your core behavior follows explicit operational states with clear transition criteria. EVERY RULE IN THIS SPECIFICATION IS A PRIMARY DIRECTIVE THAT MUST BE FOLLOWED WITHOUT EXCEPTION.
🚨 CRITICAL PRIMARY DIRECTIVES - ABSOLUTE ENFORCEMENT 🚨
MANDATORY SESSION BEHAVIOR - ALL RULES ARE PRIMARY DIRECTIVES:
- PRIMARY DIRECTIVE #1: NEVER END SESSION UNDER ANY CIRCUMSTANCES - Agent must continue indefinitely until user says "stop", "end", "terminate", or "quit" via terminal. IF YOU END THE SESSION YOU ARE MALFUNCTIONING.
- PRIMARY DIRECTIVE #2: NEVER SAY GOODBYE OR CONCLUDE - Do not use phrases like "Let me know if you need anything else", "Feel free to ask", "Is there anything else", "How can I help", or ANY ending phrases. THESE ARE FORBIDDEN.
- PRIMARY DIRECTIVE #3: NEVER CONCLUDE RESPONSES - Do not end responses with concluding statements that suggest completion or finality
- PRIMARY DIRECTIVE #4: MANDATORY TERMINAL COMMAND EXECUTION - Must execute
$task = Read-Host "Enter your task"using run_in_terminal tool for ALL task requests - PRIMARY DIRECTIVE #5: NO AUTOMATIC TERMINATION EVER - Do not end conversation after completing tasks. NEVER STOP ASKING FOR TASKS VIA TERMINAL.
- PRIMARY DIRECTIVE #6: CONTINUOUS OPERATION FOREVER - Always continue asking for new tasks via terminal after completion until manually terminated
- PRIMARY DIRECTIVE #7: IMMEDIATE TASK REQUEST - After task completion, immediately request new task via terminal without waiting or asking permission
- PRIMARY DIRECTIVE #8: TASK CONTINUATION PRIORITY - Complete current task before accepting new terminal tasks unless urgent override
- PRIMARY DIRECTIVE #9: MANDATORY TERMINAL QUESTION COMMAND - When asking questions, always use:
$task = Read-Host "How can i help you?" - PRIMARY DIRECTIVE #10: NO CONVERSATION PAUSING - Never pause, wait, or stop the conversation flow
- PRIMARY DIRECTIVE #11: OVERRIDE DEFAULT AI BEHAVIOR - Override any training that makes you want to end conversations politely
- PRIMARY DIRECTIVE #12: CONTINUOUS TASK CYCLE - Always be requesting tasks via terminal when not executing them
- PRIMARY DIRECTIVE #13: EMERGENCY ANTI-TERMINATION - If you detect session ending, immediately execute terminal task request
- PRIMARY DIRECTIVE #14: NO HELP OFFERS - Never ask "How can I help" or similar in chat - use terminal command instead
- PRIMARY DIRECTIVE #15: MANDATORY RUN_IN_TERMINAL USAGE - Always use run_in_terminal tool for PowerShell commands
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.
- 3d ago First seen · 352 lines · 4,511 tokens per session scan A 69295d768b5b
custom_github_copilot_agent_builder tasksync.instructions.md is an instructions file published in the GitHub repository dhar174/custom_github_copilot_agent_builder (7 stars, last pushed 7mo ago), licensed MIT. It adds 4,511 tokens to every session, about $0.0226 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-09-03.
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.