Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/rp1-run/rp1/echo-testnpx skills add rp1-run/rp1 --skill echo-testgit clone --depth 1 https://github.com/rp1-run/rp1Wrote 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/skills/rp1-run/rp1/echo-test)<a href="https://agentmods.dev/skills/rp1-run/rp1/echo-test"><img src="https://agentmods.dev/badge/skills/rp1-run/rp1/echo-test.svg" alt="Measured on agentmods" 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.00018 | $0.00654 |
| Opus 5 | $0.00009 | $0.00327 |
| Sonnet 5 | $0.00004 | $0.00131 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
echo-test 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Echo Test Skill
You are a validation skill for testing Copilot CLI harness primitives. Execute each step below and report results.
Parameters
This skill accepts two parameters from the user's invocation text:
- MESSAGE: The message to echo back (required)
- FORMAT: Output format -- "plain" or "json" (optional, defaults to "plain")
Parse these from the user's slash command invocation. For example:
/echo-test "hello world"-> MESSAGE="hello world", FORMAT="plain"/echo-test "hello world" json-> MESSAGE="hello world", FORMAT="json"
If MESSAGE is missing, respond with: [FIXTURE] Error: MESSAGE parameter is required. Usage: /echo-test <message> [format]
Step 1: Parameter Echo
Report the parsed parameters:
[FIXTURE] Parameters received:
MESSAGE: <parsed message>
FORMAT: <parsed format>
Step 2: Shell Execution
Run the following shell command to verify Bash tool access:
echo "[FIXTURE] Shell execution working -- $(date -u +%Y-%m-%dT%H:%M:%SZ)"
Report the output.
Step 3: File System Operations
- Read: Read the file
.rp1/context/index.mdand confirm it contains "Copilot Validation Fixture" - Write: Write the following content to
.rp1/work/echo-test-output.md:
# Echo Test Output
- Message: <MESSAGE>
- Format: <FORMAT>
- Timestamp: <current UTC time>
- Status: PASS
- Search: Use file search to find all
.mdfiles in.rp1/context/ - Edit: Append a line to
.rp1/work/echo-test-output.mdwith- Verified: true
Report each operation as PASS or FAIL.
Step 4: rp1 Agent Tools
Run the following command to verify rp1 CLI integration:
rp1 agent-tools rp1-root-dir
Report whether the command executes successfully and returns valid JSON.
Step 5: Summary
Output a summary in the requested FORMAT:
Plain format:
[FIXTURE] Echo Test Complete
Parameters: PASS/FAIL
Shell: PASS/FAIL
File Read: PASS/FAIL
File Write: PASS/FAIL
File Search: PASS/FAIL
File Edit: PASS/FAIL
Agent Tools: PASS/FAIL
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.
- 6d ago First seen · 103 lines · 18 tokens per session scan A dd6c603eecf1
echo-test is a skill published in the GitHub repository rp1-run/rp1 (38 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 654 once invoked, about $0.0001 per session on Opus 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-08-30.
Other skills, from other repositories
apm-review-panel
Use this skill to run a multi-persona expert advisory review on a labelled pull request in microsoft/apm. The panel fans out to five mandatory specialists plus a test-coverage specialist (active on every PR that touches src/) plus three conditional specialists (auth, doc-writer, performance-expert), all running in…
apm-spec-guardian
Use this skill to run a four-panel adversarial advisory review on any pull request that touches the OpenAPM specification artifact (docs/src/content/docs/specs/openapm-.md), its inline / sidecar JSON Schemas (docs/src/content/docs/specs/schemas/.schema.json), or the conformance fixture seed…
apm-triage-panel
Use this skill to triage one microsoft/apm issue selected by the daily sweep, the status/needs-triage fast path, or manual dispatch. Emit one synthesized comment with a decision, label set, exact milestone, and suggested next action.
cli-logging-ux
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (richsuccess, richwarning, richerror, richinfo, richecho), DiagnosticCollector, STATUSSYMBOLS, CommandLogger, or any…
pr-description-skill
Use this skill to write the PR description (PR body) for any pull request opened against microsoft/apm. Produces one self-sufficient GitHub-Flavored Markdown artifact: TL;DR, Problem (WHY), Approach (WHAT), Implementation (HOW), 1-3 validated mermaid diagrams, explicit trade-offs, validation evidence, and a…
docs-sync
Use this skill whenever a pull request is opened, reopened, or synchronized in microsoft/apm to assess whether and how the documentation corpus must change to stay truthful with the proposed code change. Activate even when the PR title or body says nothing about docs -- the skill must run on every PR to detect silent…