A pull-request review that checks whether changed code follows the repository's written coding standards. It is separate from checking whether the requested feature works, or whether the code passes syntax, lint, and formatting checks.

Use it to inspect a pull request against files such as CODING_STANDARDS.md, report genuine violations with locations and severity, and give a short overall summary.

It keeps standards review focused on documented rules and avoids mixing style findings with product requirements or automated checks.

How hakeemrabiuDFW/Tanda-Workforce-MCP-Server configures GitHub Copilo

Reuse

Borrowing it

Nothing to install: this file belongs to hakeemrabiuDFW/Tanda-Workforce-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/hakeemrabiuDFW/Tanda-Workforce-MCP-Server/main/.github/prompts/standards.md

Clone the repo

git clone --depth 1 https://github.com/hakeemrabiuDFW/Tanda-Workforce-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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/hakeemrabiudfw/tanda-workforce-mcp-server/standards/github.svg)](https://agentmods.dev/commands/hakeemrabiudfw/tanda-workforce-mcp-server/standards)

Your own site

<a href="https://agentmods.dev/commands/hakeemrabiudfw/tanda-workforce-mcp-server/standards"><img src="https://agentmods.dev/badge/commands/hakeemrabiudfw/tanda-workforce-mcp-server/standards/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/commands/hakeemrabiudfw/tanda-workforce-mcp-server/standards"><img src="https://agentmods.dev/badge/commands/hakeemrabiudfw/tanda-workforce-mcp-server/standards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 229 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00229
Opus 5.5	$0.00000	$0.00092
Sonnet 5.5	$0.00000	$0.00046
Haiku 4.5	$0.00000	$0.00023

Measured 5d ago against content hash 4cc1fea426ec, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

standards 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 5d 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.

.github/prompts/standards.md · 24 lines

What it actually says

Standards reviewer

Judge whether this PR follows the repo's documented standards. Nothing else: whether it does what was asked is the Spec reviewer's job, and lint, syntax and formatting are the checks job's.

Read

CODING_STANDARDS.md: the rubric. Its Blocking and Non-blocking sections set the severity of each finding.
AGENTS.md and GLOSSARY.md, if present: conventions and vocabulary.
.review/diff.patch: the change. Open the changed files when you need the surrounding code.

Report

One finding per real problem in the changed lines, citing the standard it breaks. Give file and line (line in the new file) when you can.
blocking only when it breaks a rule in the Blocking section. Everything else is non-blocking.
No findings is a good result. Do not pad, and do not comment on code the PR did not touch.
summary: one or two sentences on the PR as a whole.

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.

5d ago First seen · 24 lines · 0 tokens per session scan A 4cc1fea426ec

Subscribe to this mod's changes

standards is a command published in the GitHub repository hakeemrabiuDFW/Tanda-Workforce-MCP-Server (2 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 229 tokens. 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-24.

Code review

Tanda-Workforce-MCP-Server: Command for GitHub Copilot

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Standards reviewer

Read

Report

What this file has done since we first saw it

Other commands, from other repositories

refactor

review-branch

init

spec-trace-requirements

merge-conflict-analysis

boot