Meshtastic-Android is an Android and Compose Desktop app for communicating through open-source mesh radios, which relay messages between nearby devices instead of relying on a conventional network. It is used with Meshtastic devices for messaging, node and channel discovery, location features, telemetry, and device management.
Borrowing it
Nothing to install: this file belongs to meshtastic/Meshtastic-Android. 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/meshtastic/Meshtastic-Android/main/.github/prompts/speckit.specify.prompt.mdgit clone --depth 1 https://github.com/meshtastic/Meshtastic-AndroidWrote 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/commands/meshtastic/meshtastic-android/speckit.specify)<a href="https://agentmods.dev/commands/meshtastic/meshtastic-android/speckit.specify"><img src="https://agentmods.dev/badge/commands/meshtastic/meshtastic-android/speckit.specify/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/commands/meshtastic/meshtastic-android/speckit.specify"><img src="https://agentmods.dev/badge/commands/meshtastic/meshtastic-android/speckit.specify.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.00000 | $0.00010 |
| Opus 5.5 | $0.00000 | $0.00004 |
| Sonnet 5.5 | $0.00000 | $0.00002 |
| Haiku 4.5 | $0.00000 | $0.00001 |
Grade A, and why
speckit.specify 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 1mo ago First seen · 4 lines · 0 tokens per session scan A 7b2cc4dc6462
speckit.specify is a command published in the GitHub repository meshtastic/Meshtastic-Android (1,894 stars, last pushed today), licensed GPL-3.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-09-07.
Other commands, from other repositories
feat
Kick off tasks creation for a new feature (4-item interview before invoking pm-agent; an epic-sized requirement routes to phased decomposition, a feature already built on one platform routes to cross-platform parity, a change that touches no endpoint routes to client-only).
feature-build
Build a complete mobile feature from description to running code with E2E tests. Orchestrates 6 phases - planning, implementation, testing, build-fix, quality gate, and verification. Auto-detects platform.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.