agentmods.dev

f5xc-api-mcp: Instructions file for Claude Code

CLAUDE.md

f5xc-api-mcp CLAUDE.md is an instructions file for Claude Code from robinmordasiewicz/f5xc-api-mcp. It costs 2,137 tokens per session, scanned A, a copy of f5xc-cloudstatus-mcp CLAUDE.md, MIT.

Repository workflow instructions for a project that uses GitHub issues, branches, pull requests, automated checks, and automatic merging. A pull request is a proposed change that must pass review or checks before entering the main branch.

In plain words
What is it for?
Use them when making changes in the f5xc-api-mcp repository, including creating an issue, opening a pull request, monitoring CI, and checking post-merge workflows.
Why use it?
They define the required path from planning a change through CI fixes, merging, post-merge checks, and local branch cleanup.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions Claude Code.

This is robinmordasiewicz/f5xc-api-mcp's own configuration. It tells Claude Code how to work on f5xc-api-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything f5xc-api-mcp configures →

not rated 1repo 3mo ago A scan 2,137 tokens copy · 100% MIT archived
View source ↗ robinmordasiewicz/f5xc-api-mcp robinmordasiewicz.github.io
Reuse

Borrowing it

Nothing to install: this file belongs to robinmordasiewicz/f5xc-api-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/robinmordasiewicz/f5xc-api-mcp/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/robinmordasiewicz/f5xc-api-mcp

Made for: Claude Code.

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.

agentmods badge for f5xc-api-mcp CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/robinmordasiewicz/f5xc-api-mcp/claude-md.svg)](https://agentmods.dev/instructions/robinmordasiewicz/f5xc-api-mcp/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/robinmordasiewicz/f5xc-api-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/robinmordasiewicz/f5xc-api-mcp/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 2,137 This file is loaded in full into every session.
When invoked 2,137 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 100% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.02137 $0.02137
Opus 5 $0.01069 $0.01069
Sonnet 5 $0.00427 $0.00427
Haiku 4.5 $0.00214 $0.00214

Measured 7d ago against content hash 80b2e055f189, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

f5xc-api-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 7d 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.

Origin

This is a copy

100% identical to f5xc-cloudstatus-mcp CLAUDE.md — 0 lines 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.

CLAUDE.md · 282 lines

How it starts

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

Claude Code Project Instructions

Repository Workflow

This repo enforces a strict governance workflow. DO NOT STOP after creating a PR — the task is not complete until the PR is merged, all post-merge workflows succeed, and local branches are cleaned.

Making Changes (Steps 1-5)

  1. Create a GitHub issue before making any changes
  2. Create a feature branch from main — never commit to main directly
  3. Commit changes with conventional format (feat:, fix:, docs:) and push to remote
  4. Open a PR that links to the issue using Closes #N — fill out the PR template completely
  5. Fix any CI failures — monitor checks with gh pr checks <NUMBER>, fix locally, push to trigger re-runs

Waiting for Auto-Merge (Step 6)

  1. Wait for auto-merge — PRs merge automatically (squash) once all CI checks pass. Poll until the PR state is MERGED:

    gh pr view <NUMBER> --json state --jq '.state'

    If the PR is not merging, check for issues:

    gh pr view <NUMBER> --json mergeable,mergeStateStatus

Post-Merge Monitoring (Steps 7-8)

  1. Monitor post-merge workflows — merging to main triggers additional workflows (docs builds, governance sync, etc.). Discover and watch them:

    git checkout main && git pull origin main
MERGE_SHA=$(git rev-parse HEAD)
sleep 10
gh run list --branch main --commit $MERGE_SHA
gh run watch <RUN-ID> --exit-status

  2. Iterate on failures — if any workflow fails:

    • View logs: gh run view <RUN-ID> --log-failed
    • Analyze the root cause
    • Fix the code locally
    • Create a new issue, branch, and PR with the fix
    • Return to Step 5 and repeat until all workflows pass
    • For pre-existing failures unrelated to your changes: create a GitHub issue (per CI Monitoring rules below) and continue

Cleanup (Steps 9-10)

  1. Clean up branches — only after all workflows succeed. Delete your feature branch and any other stale local branches already merged to main:

Read the full file on GitHub · 282 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.

  1. 7d ago First seen · 282 lines · 2,137 tokens per session scan A 80b2e055f189

Subscribe to this mod's changes

f5xc-api-mcp CLAUDE.md is an instructions file published in the GitHub repository robinmordasiewicz/f5xc-api-mcp (1 stars, last pushed 3mo ago), licensed MIT. It adds 2,137 tokens to every session, about $0.0107 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to f5xc-cloudstatus-mcp CLAUDE.md, differing in 0 lines, and is treated as a copy.

CommitsGit and workflowProject managementapif5xcmcp
Related

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.

openai/codex · 5,153 tokens

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

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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.

langchain-ai/langchain · 4,469 tokens

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

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens