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 commands/chen-zexi/open-ptc-agent/pre-commitgit clone --depth 1 https://github.com/Chen-zexi/open-ptc-agentWhat 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 | $0.00018 | $0.00391 |
| Opus 5 | $0.00009 | $0.00196 |
| Sonnet 5 | $0.00004 | $0.00078 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
pre-commit 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 3d 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
Pre-Commit Check
Run all CI checks locally before committing. This matches the GitHub CI workflow exactly.
Your Task
Run these checks in order, stopping if any fail:
1. Lint (ruff check)
uv run ruff check libs/ptc-agent/ptc_agent/ libs/ptc-agent/tests/
uv run ruff check libs/ptc-cli/ptc_cli/ libs/ptc-cli/tests/
If there are auto-fixable issues, fix them:
uv run ruff check libs/ptc-agent/ptc_agent/ libs/ptc-agent/tests/ --fix
uv run ruff check libs/ptc-cli/ptc_cli/ libs/ptc-cli/tests/ --fix
2. Type Check (mypy)
cd libs/ptc-agent && uv run mypy ptc_agent/
cd libs/ptc-cli && uv run mypy ptc_cli/
3. Unit Tests
uv run pytest libs/ptc-agent/tests/unit_tests/ -v
uv run pytest libs/ptc-cli/tests/unit_tests/ -v
4. Integration Tests
uv run pytest libs/ptc-agent/tests/integration_tests/ -v
uv run pytest libs/ptc-cli/tests/integration_tests/ -v
Note: Integration tests require DAYTONA_API_KEY and ANTHROPIC_API_KEY environment variables.
Summary
Report results for each step:
- Lint: PASS/FAIL
- Type check: PASS/FAIL
- Unit tests: PASS/FAIL
- Integration tests: PASS/FAIL/SKIPPED (if env vars missing)
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.
- 3d ago First seen · 56 lines · 18 tokens per session scan A a47212eb803c
pre-commit is a command published in the GitHub repository Chen-zexi/open-ptc-agent (730 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 391 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 commands, from other repositories
date
询问当天的日期,输出的格式为 yyyy-MM-dd 星期几.
generate-prd
Generate a comprehensive Product Requirements Document for the following feature.
plan
Take the following feature description and create a comprehensive, structured implementation plan.
execute-prd
Implement a feature by following a Product Requirements Document step by step.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
axstream-teach
Compile a UI task into a fast replayable macro (do it once, instant forever).