fubon-api-mcp-server: Command for GitHub Copilot

.github/prompts/write-coding-standards-from-file.prompt.md

write-coding-standards-from-file is a command for GitHub Copilot from Mofesto/fubon-api-mcp-server. It costs 29 tokens per session (3,655 once invoked), scanned A, original, Apache-2.0.

A command that creates a project coding-standards document from the style used in supplied files or folders. Coding standards are shared rules for how source code should be formatted and organised.

In plain words
What is it for?
Use it to document style rules from example files, optionally add them to a README, and create or update a standards file.
Why use it?
It turns an existing codebase's conventions into written guidance, reducing disagreements and inconsistent new code. It can also identify and address inconsistencies according to its configuration.

Command for GitHub Copilot

Written for GitHub Copilot: a Copilot chat mode or prompt. Also seen: agent in frontmatter.

This is Mofesto/fubon-api-mcp-server's own configuration. It tells GitHub Copilot how to work on fubon-api-mcp-server 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 fubon-api-mcp-server configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Mofesto/fubon-api-mcp-server. 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/Mofesto/fubon-api-mcp-server/main/.github/prompts/write-coding-standards-from-file.prompt.md
Clone the repo
git clone --depth 1 https://github.com/Mofesto/fubon-api-mcp-server

Made for: GitHub Copilot.

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 write-coding-standards-from-file

README.md
[![agentmods](https://agentmods.dev/badge/commands/mofesto/fubon-api-mcp-server/write-coding-standards-from-file/github.svg)](https://agentmods.dev/commands/mofesto/fubon-api-mcp-server/write-coding-standards-from-file)
Your own site
<a href="https://agentmods.dev/commands/mofesto/fubon-api-mcp-server/write-coding-standards-from-file"><img src="https://agentmods.dev/badge/commands/mofesto/fubon-api-mcp-server/write-coding-standards-from-file/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.

agentmods 80×15 button for write-coding-standards-from-file

Your own site · 80×15
<a href="https://agentmods.dev/commands/mofesto/fubon-api-mcp-server/write-coding-standards-from-file"><img src="https://agentmods.dev/badge/commands/mofesto/fubon-api-mcp-server/write-coding-standards-from-file.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,655 The whole file, excluding the scripts and references it only reads on demand.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.03655
Opus 5.5 $0.00012 $0.01462
Sonnet 5.5 $0.00006 $0.00731
Haiku 4.5 $0.00003 $0.00365

Measured yesterday against content hash 92b7de2eee7e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

write-coding-standards-from-file 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 yesterday.

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.

.github/prompts/write-coding-standards-from-file.prompt.md · 317 lines

How it starts

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

Write Coding Standards From File

Use the existing syntax of the file(s) to establish the standards and style guides for the project. If more than one file or a folder is passed, loop through each file or files in the folder, appending the file's data to temporary memory or a file, then when complete use temporary data as a single instance; as if it were the file name to base the standards and style guideline on.

Rules and Configuration

Below is a set of quasi-configuration boolean and string[] variables. Conditions for handling true, or other values for each variable are under the level two heading ## Variable and Parameter Configuration Conditions.

Parameters for the prompt have a text definition. There is one required parameter ${fileName}, and several optional parameters ${folderName}, ${instructions}, and any [configVariableAsParameter].

Configuration Variables

  • addStandardsTest = false;
  • addToREADME = false;
  • addToREADMEInsertions = ["atBegin", "middle", "beforeEnd", "bestFitUsingContext"];
    • Default to beforeEnd.
  • createNewFile = true;
  • fetchStyleURL = true;
  • findInconsistencies = true;
  • fixInconsistencies = true;
  • newFileName = ["CONTRIBUTING.md", "STYLE.md", "CODE_OF_CONDUCT.md", "CODING_STANDARDS.md", "DEVELOPING.md", "CONTRIBUTION_GUIDE.md", "GUIDELINES.md", "PROJECT_STANDARDS.md", "BEST_PRACTICES.md", "HACKING.md"];
    • For each file in ${newFileName}, if file does not exist, use that file name and break, else continue to next file name of ${newFileName}.
  • outputSpecToPrompt = false;
  • useTemplate = "verbose"; // or "v"
    • Possible values are [["v", "verbose"], ["m", "minimal"], ["b", "best fit"], ["custom"]].
    • Selects one of the two example templates at the bottom of prompt file under the level two heading ## Coding Standards Templates, or use another composition that is a better fit.
    • If custom, then apply per request.

Configuration Variables as Prompt Parameters

If any of the variable names are passed to prompt as-is, or as a similar but clearly related text value, then override the default variable value with the value passed to prompt.

Read the full file on GitHub · 317 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. yesterday First seen · 317 lines · 29 tokens per session scan A 92b7de2eee7e

Subscribe to this mod's changes

write-coding-standards-from-file is a command published in the GitHub repository Mofesto/fubon-api-mcp-server (17 stars, last pushed yesterday), licensed Apache-2.0. It adds 29 tokens to every session and 3,655 once invoked, about $0.0001 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-10-20.