Borrowing it
Nothing to install: this file belongs to phamviet86/google-task-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.
curl -O https://raw.githubusercontent.com/phamviet86/google-task-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/phamviet86/google-task-mcpWrote 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/phamviet86/google-task-mcp/agents-md)<a href="https://agentmods.dev/instructions/phamviet86/google-task-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/phamviet86/google-task-mcp/agents-md/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/phamviet86/google-task-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/phamviet86/google-task-mcp/agents-md.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.00700 | $0.00700 |
| Opus 5.5 | $0.00280 | $0.00280 |
| Sonnet 5.5 | $0.00140 | $0.00140 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
google-task-mcp AGENTS.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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent contract
This repository is a local, stdio-only MCP server for one authenticated Google Tasks account. Keep
the repository name google-task-mcp, the console commands google-tasks-mcp and
google-tasks-mcp-auth, and the unique distribution name phamviet-google-tasks-mcp distinct.
Operating rules
- Never read, create, commit, print, or request OAuth client secrets, authorization codes, refresh
tokens, token files, real task content, or unredacted client configuration during ordinary work.
A live authenticated read is allowed only when a maintainer explicitly authorizes it and provides a
dedicated non-production Google account containing only test data. Otherwise do not invoke a
Google tool and record the authenticated-read check as
NOT_VERIFIED. - Treat Google Tasks as external user data. In a maintainer-authorized interaction, read before
modifying when context matters; ask for explicit user confirmation before
delete_task_list,delete_task, orclear_completed_tasks. - Do not represent MCP initialization or tool discovery as an authentication test. Discovery works without credentials; a real tool call requires a valid token.
- Preserve stdio-only operation. Do not add a listener, database, background service, sync job, or webhook without an explicit architecture decision.
- Use absolute executable and token paths in client examples. Keep local tokens outside the checkout.
- macOS and Linux are the current supported release platforms. Do not claim Windows support until permission handling and end-to-end operation are verified.
Change contract
When behavior changes, keep README.md, README.vi.md, docs/release-deployment.md, and tests in
sync with the runtime schema. Preserve the 14-tool public contract unless a versioned compatibility
decision explicitly changes it. Maintain the difference between omitted update fields and explicit
null for clearing notes or due.
The packaged google-tasks-setup and google-tasks skills are user-facing onboarding assets.
Keep them concise, secret-free, and usable from an installed distribution. Their setup guidance must
distinguish local token metadata, MCP discovery, and successful authenticated API access; a live
read remains subject to the authorization boundary above. Document commands only in a release that
actually contains them. Do not claim a release is published until its tagged GitHub Release assets
have been verified as available.
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 Changed · +7 lines · +102 tokens per session 1ed1e0859dea
- 1mo ago First seen · 47 lines · 598 tokens per session scan A 40b43a49ed5b
google-task-mcp AGENTS.md is an instructions file published in the GitHub repository phamviet86/google-task-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 700 tokens to every session, about $0.0028 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-09-04.
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).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.