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/SyntaxArc/archipy-pluginWrote 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/rules/syntaxarc/archipy-plugin/tooling-for-apps)<a href="https://agentmods.dev/rules/syntaxarc/archipy-plugin/tooling-for-apps"><img src="https://agentmods.dev/badge/rules/syntaxarc/archipy-plugin/tooling-for-apps.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.00313 | $0.00313 |
| Opus 5 | $0.00156 | $0.00156 |
| Sonnet 5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
tooling-for-apps 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 today.
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
Tooling for ArchiPy Apps
Package Management
Use uv; never install project packages with bare pip.
uv sync
uv add "archipy[redis,fastapi]"
uv add --group dev ruff ty pre-commit
- Inspect
pyproject.tomlbefore adding dependencies; do not duplicate an existing direct/transitive requirement. - Install only ArchiPy extras required by the app.
- Commit
uv.lockchanges when dependency changes are intentional.
Project Commands
Prefer commands already defined by the app's Makefile, pyproject.toml, task runner, or CI. Do not assume ArchiPy
library Make targets exist. When no wrapper exists, typical direct checks are:
uv run ruff format .
uv run ruff check .
uv run ty check
uv run behave features/example.feature
uv run pre-commit run --all-files
Run the narrowest relevant test during iteration, then the app's complete required gate before handoff. Use Behave as the primary ArchiPy acceptance-test style; follow project-specific unit-test tooling when present.
Hooks
If the app configures pre-commit, install/run it through uv. Do not add or rewrite hook configuration unless the task
requires tooling changes. Fix generated formatting/lint changes before reporting completion.
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.
- today First seen · 42 lines · 313 tokens per session scan A 01005944f42a
tooling-for-apps is a cursor rule published in the GitHub repository SyntaxArc/archipy-plugin (2 stars, last pushed today), licensed MIT. It adds 313 tokens to every session, about $0.0016 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-09-08.
Other cursor rules, from other repositories
test-engineer
Test Engineer agent.
playwright-integration-testing-cursorrules-prompt-file
Cursor rules for Playwright development with integration testing.
cypress-integration-testing-cursorrules-prompt-file
Cursor rules for Cypress development with integration testing.
playwright-api-testing-cursorrules-prompt-file
Cursor rules for Playwright development with API testing.
playwright-e2e-testing-cursorrules-prompt-file
Cursor rules for Playwright development with E2E testing.
ci-cd
CI/CD pipeline patterns and deployment rules.