uno: Command for GitHub Copilot

.github/prompts/speckit.git.validate.prompt.md

speckit.git.validate is a command for GitHub Copilot from unoplatform/uno. It costs 0 tokens per session (10 once invoked), scanned A, original, Apache-2.0.

A command that checks whether the current Git branch follows the project’s feature-branch naming rules. It also checks whether the matching feature specification directory exists under specs/.

In plain words
What is it for?
Use it to validate numbered or timestamp-based feature branches and find their corresponding specification directory.
Why use it?
It catches branch names or missing specification folders that do not match the project’s expected workflow.

Command for GitHub Copilot

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

This is unoplatform/uno's own configuration. It tells GitHub Copilot how to work on uno 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 uno configures →

About the project

Uno Platform is an open-source .NET development platform that lets developers build native mobile, web, desktop, and embedded applications from one C# and XAML codebase. It is intended for .NET developers who want to share application code across multiple operating systems and device types. The catalogue entries support development workflows for Uno Platform with skills, agents, commands, and instructions.

unoplatform/uno · 10,080 stars · on GitHub · platform.uno

Reuse

Borrowing it

Nothing to install: this file belongs to unoplatform/uno. 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/unoplatform/uno/master/.github/prompts/speckit.git.validate.prompt.md
Clone the repo
git clone --depth 1 https://github.com/unoplatform/uno

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 speckit.git.validate

README.md
[![agentmods](https://agentmods.dev/badge/commands/unoplatform/uno/speckit.git.validate/github.svg)](https://agentmods.dev/commands/unoplatform/uno/speckit.git.validate)
Your own site
<a href="https://agentmods.dev/commands/unoplatform/uno/speckit.git.validate"><img src="https://agentmods.dev/badge/commands/unoplatform/uno/speckit.git.validate/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 speckit.git.validate

Your own site · 80×15
<a href="https://agentmods.dev/commands/unoplatform/uno/speckit.git.validate"><img src="https://agentmods.dev/badge/commands/unoplatform/uno/speckit.git.validate.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 10 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.00000 $0.00010
Opus 5.5 $0.00000 $0.00004
Sonnet 5.5 $0.00000 $0.00002
Haiku 4.5 $0.00000 $0.00001

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

Security

Grade A, and why

speckit.git.validate 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.

Origin

Copies of this mod

8 near-identical copies found in the catalogue:

.github/prompts/speckit.git.validate.prompt.md · 4 lines

The source is not reproduced here

Licensed Apache-2.0

The repository is licensed Apache-2.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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. 1mo ago Changed · -46 lines · -8 tokens per session 0f29e55cbfbf
  2. 1mo ago First seen · 50 lines · 8 tokens per session scan A d8f8e5ecc52e

Subscribe to this mod's changes

speckit.git.validate is a command published in the GitHub repository unoplatform/uno (10,080 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 10 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-08-30.