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.
git clone --depth 1 https://github.com/bartstc/vite-ts-react-templateWrote 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/bartstc/vite-ts-react-template/create-pr)<a href="https://agentmods.dev/commands/bartstc/vite-ts-react-template/create-pr"><img src="https://agentmods.dev/badge/commands/bartstc/vite-ts-react-template/create-pr/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/bartstc/vite-ts-react-template/create-pr"><img src="https://agentmods.dev/badge/commands/bartstc/vite-ts-react-template/create-pr.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.00243 |
| Opus 5.5 | $0.00000 | $0.00097 |
| Sonnet 5.5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
create-PR 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.
What it actually says
Create a PR against this branch: $ARGUMENTS.
Follow these steps:
- ALWAYS start by running
git statusto check what branch you're on - Use this template:
gh pr create --base core --head <branch_name> --title "very clear & concise title" --body "clear, detailed description of changes" - Always create Pull Requests against the branch the user specifics.
- If you run into issues, STOP and explain the error to the user.
Remember:
- DO NOT CREDIT YOURSELF in the PR's description
- Especially do not add this at the end: 🤖 Generated with Claude Code
- Use the GitHub CLI (
gh) for all GitHub-related tasks - Make titles clear & concise; make descriptions detailed yet focused, without testing plan; never credit yourself
- Define titles following Conventional Commits specification:
- for fixes, prefix with "fix: "
- for new features, prefix with "feat: "
- for edits, prefix with "chore: "
- Example:
fix: resolve logout bug,feat: add login form
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 · 21 lines · 0 tokens per session scan A 01aad066f1fc
create-PR is a command published in the GitHub repository bartstc/vite-ts-react-template (122 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 243 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.
Other commands, from other repositories
release-commands
:::info This document covers the release and changelog commands for publishing eIsland builds and generating release notes. For packaging the installer locally, see Package Commands. ::.
plugin-commands
:::info This document covers all build, test, and smoke commands for eIsland native plugins. Windows plugins live under plugins/windows/; macOS helpers live under plugins/macos/. Each plugin has its own package.json with independent scripts. ::.
e2e-testing
:::info The Playwright suite launches the real Electron main process and built React UI on Windows and macOS. It exercises the preload bridge, IPC handlers, and file storage. See Testing Commands for the separate Vitest suite. ::.
quality-commands
:::info This document covers all code quality commands for the eIsland project — ESLint, Stylelint, HTML validation, comment checks, and i18n completeness. ::.
esa-commands
:::info This document covers the ESA (Edge Security Acceleration) CDN cache purge commands for clearing cached content on Alibaba Cloud ESA. These commands use the official @alicloud/esa20240910 SDK. ::.
package-commands
:::info This document covers the packaging and lifecycle commands for building distributable installers and managing native modules. For development commands (dev, build, preview), see Development Commands. ::.