Borrowing it
Nothing to install: this file belongs to peturgeorgievv-factory/postfast-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/peturgeorgievv-factory/postfast-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/peturgeorgievv-factory/postfast-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/peturgeorgievv-factory/postfast-mcp/claude-md)<a href="https://agentmods.dev/instructions/peturgeorgievv-factory/postfast-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/peturgeorgievv-factory/postfast-mcp/claude-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/peturgeorgievv-factory/postfast-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/peturgeorgievv-factory/postfast-mcp/claude-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.00687 | $0.00687 |
| Opus 5 | $0.00344 | $0.00344 |
| Sonnet 5 | $0.00137 | $0.00137 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
postfast-mcp CLAUDE.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 11d 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 — 19 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Public stdio MCP server (npm: postfast-mcp) over PostFast's pf-api-key REST API — and the home of the shared tool catalog (src/core, exported as postfast-mcp/core). The deployed remote twin ../social-schedule-mcp (mcp.postfa.st) consumes the catalog too — its adapter landed 2026-08-05 (src/mcp/mcp.service.ts + gateway.adapter.ts import postfast-mcp/core), and a release here auto-bumps it (Release step 3).
Rules
- Source of truth is the backend:
../social-schedule-service— itsdocs/periphery.mdholds the constellation map (repos, verify commands, release channels). - Tool descriptions ARE the API — models discover fields only from descriptions/schemas, so wording changes are behavior changes. Keep them accurate against the BE REST responses.
- The catalog IS the single source: every tool (schema + description + title + annotations + outputSchema + binding) lives ONLY in
src/core/tools/. Never author tool text anywhere else; both bindings render from it. - stdio surface stability:
scripts/parity-diff.mjsdiffs a published version against the local build (initialize + tools/list over real stdio). Run it before any release that touches the catalog. - Workflow security:
release.yml's dispatch authenticates as the release-bot GitHub App (RELEASE_BOT_APP_ID+RELEASE_BOT_PRIVATE_KEY; the private key is the critical credential) — it mints a short-lived token scoped to social-schedule-mcp only. Reference secrets ONLY on the step that uses them, never job/workflow level. This repo must NEVER gain apull_request_targetworkflow that checks out PR code, and no secret-bearing workflow may interpolate PR-controlled strings (titles, branch names, bodies). - Never commit with AI/Claude attribution or Co-authored-by.
Release (tag-triggered — CI holds no credentials)
- Every behavior-changing PR adds a
.changeset/*.md(patch/minor + summary). - To release:
npm run version(changesets computes the bump + CHANGELOG,scripts/stamp-versions.mjsstamps manifest.json, server.json, both.claude-plugin/files,src/stdio/index.ts, package-lock.json) → review the diff → commit ("…, bump to X" style). - Pushing the tag is the publish button:
git tag vX.Y.Z && git push origin main vX.Y.Z.release.ymlthen publishes npm (trusted publishing/OIDC), the MCP Registry (github-oidc), and a GitHub Release with the.mcpbattached. A tag that doesn't match package.json fails fast. Thecatalog-releaserepository_dispatch then wakessocial-schedule-mcp'scatalog-bump.yml, which waits for npm to serve the version, pins it exactly, commits[skip ci], and triggers its Docker build — the host picks up the new catalog with nothing further to do here. Registry hiccup? Re-run via the workflow's manualworkflow_dispatch(registry-republish job).
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.
- 11d ago First seen · 19 lines · 687 tokens per session scan A ead21e62a2f7
postfast-mcp CLAUDE.md is an instructions file published in the GitHub repository peturgeorgievv-factory/postfast-mcp (5 stars, last pushed 17d ago), licensed MIT. It adds 687 tokens to every session, about $0.0034 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-08-31.
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).
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.
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).