What is tickadoo-mcp AGENTS.md?

A repository instruction file for AI coding agents working on the tickadoo MCP server, an interface that lets agents use tickadoo services.

It is for guiding coding tasks in this repository, including choosing GitHub Issues instead of the retired Linear process and following repository policies.

It gives agents shared rules for starting work, tracking issues, making activity visible in Slack, and formatting commits.

How tickadoo/tickadoo-mcp configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to tickadoo/tickadoo-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.

Copy the file

curl -O https://raw.githubusercontent.com/tickadoo/tickadoo-mcp/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/tickadoo/tickadoo-mcp

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/tickadoo/tickadoo-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/tickadoo/tickadoo-mcp/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/tickadoo/tickadoo-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/tickadoo/tickadoo-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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/tickadoo/tickadoo-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/tickadoo/tickadoo-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 2,265 This file is loaded in full into every session.

When invoked 2,265 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.02265	$0.02265
Opus 5.5	$0.00906	$0.00906
Sonnet 5.5	$0.00453	$0.00453
Haiku 4.5	$0.00227	$0.00227

Measured 1mo ago against content hash ea652621232d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

tickadoo-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.

AGENTS.md · 138 lines

How it starts

The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md — Shared instructions for AI coding agents

This file is automatically read by Codex CLI (and some other AI coding tools) at task start. It's the shared ruleset for every AI agent that does work on this repo: Claude chats, Claude Code sessions, and Codex tasks.

This repo is @tickadoo/mcp-server — the npm distribution of the public tickadoo MCP server for its live experiences catalogue. Since v2.0.0 it is a thin remote bridge that proxies to the canonical remote server at https://mcp.tickadoo.com/mcp. The remote server and the embeddable widget bundle live in HowardOS (github.com/tickadoo/howard), which is canonical; this repo ships only the stdio bridge.

Issue tracking: GitHub Issues (Linear frozen 2026-08-18)

New work is a GitHub issue #NNNN in this repo, on the shared Project board. Do not open Linear issues.

Legacy GRO- / BAC- / TIC- IDs are read-only historical references and resolve to tickadoo/linear-archive, never to a GitHub issue number. Grep that repo rather than calling an API. All three namespaces are frozen; never mint a new one.

Canonical policy lives in tickadoo/howard: AGENTS.md → "Issue tracking" and docs/operations/linear-to-github-issues.md.

Before you do anything

Pull first: run git pull --rebase origin main at task start. Codex worktrees (see .claude/worktrees/) may be stale clones; without a pull you may be reading an old version of this file or CLAUDE.md that predates recent changes.
Check Hive before editing: use the claude_platform tools to inspect presence, recent activity, inboxes, reservations, and blockers for tickadoo/tickadoo-mcp. Reserve the paths you intend to edit and release them after handoff or completion. If Hive is unavailable, presence is unknown: inspect open pull requests, use a narrow isolated branch, and ask the human dispatcher when material overlap remains possible. Never use Slack as a coordination input.
Read CLAUDE.md (if present — a minimal one lives at repo root). Also read the HowardOS repo CLAUDE.md (github.com/tickadoo/howard → CLAUDE.md) for the broader tickadoo project context (supplier pipeline, booking flows, content rules, team). Anything in the HowardOS CLAUDE.md that applies to the MCP server applies here too.
Before each push: git pull --rebase origin main again. Multiple agents push to main concurrently — racing is the default, not the exception.

Read the full file on GitHub · 138 lines

Changes

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 · -14 lines · -120 tokens per session ea652621232d
1mo ago Changed · -8 tokens per session 69b0c48ec716
2mo ago First seen · 152 lines · 2,393 tokens per session scan A 1706b6950721

Subscribe to this mod's changes

tickadoo-mcp AGENTS.md is an instructions file published in the GitHub repository tickadoo/tickadoo-mcp (2 stars, last pushed 3d ago), licensed MIT. It adds 2,265 tokens to every session, about $0.0091 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.

gemini-cli-extension

tickadoo-mcp AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
tickadoo-mcp AGENTS.mdtickadoo/tickadoo-mcp	Instructions file	2	3d ago	MIT	A	2,265	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

tickadoo-mcp: Instructions file for Codex