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/pymodel/pythinker-cli/pythinker-code-helpnpx skills add PyModel/pythinker-cli --skill pythinker-code-helpgit clone --depth 1 https://github.com/PyModel/pythinker-cliWhat 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.00063 | $0.00500 |
| Opus 5 | $0.00032 | $0.00250 |
| Sonnet 5 | $0.00013 | $0.00100 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
pythinker-code-help 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 2d 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
Pythinker CLI Help
Help users with Pythinker CLI questions by consulting documentation and source code.
Strategy
- Prefer official documentation for most questions
- Read local source when in pythinker-code project itself, or when user is developing with pythinker-code as a library (e.g., importing from
pythinker_codein their code) - Clone and explore source for complex internals not covered in docs - ask user for confirmation first
Documentation
Base URL: https://pythoughts-labs.github.io/pythinker-cli/
Fetch documentation index to find relevant pages:
https://pythoughts-labs.github.io/pythinker-cli/llms.txt
Page URL Pattern
- Pages:
https://pythoughts-labs.github.io/pythinker-cli/en/...
Topic Mapping
| Topic | Page |
|---|---|
| Installation, first run | /en/guides/getting-started.md |
| Config files | /en/configuration/config-files.md |
| Providers, models | /en/configuration/providers.md |
| Environment variables | /en/configuration/env-vars.md |
| Slash commands | /en/reference/slash-commands.md |
| CLI flags | /en/reference/pythinker-command.md |
| Keyboard shortcuts | /en/reference/keyboard.md |
| MCP | /en/customization/mcp.md |
| Agents | /en/customization/agents.md |
| Skills | /en/customization/skills.md |
| FAQ | /en/faq.md |
Source Code
Repository: https://github.com/Pythoughts-labs/pythinker-cli
When to read source:
- In pythinker-code project directory (check
pyproject.tomlforname = "pythinker-code") - User is importing
pythinker_codeas a library in their project - Question about internals not covered in docs (ask user before cloning)
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.
- 2d ago First seen · 55 lines · 63 tokens per session scan A f97415c6a8f3
pythinker-code-help is a skill published in the GitHub repository PyModel/pythinker-cli (20 stars, last pushed 5d ago), licensed Apache-2.0. It adds 63 tokens to every session and 500 once invoked, about $0.0003 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
release-notes
Generate user-facing release notes for Intelligent Terminal. Use when asked to write release notes, changelog, what-is-new summary, or prepare a release. Compares git commits between releases, looks up PR-linked issues and community contributors, then outputs formatted notes with "Verbed + Impact + Scenario" style…
peer-review
Structured manuscript/grant review with checklist-based evaluation. Use when writing formal peer reviews with specific criteria methodology assessment, statistical validity, reporting standards compliance (CONSORT/STROBE), and constructive feedback. Best for actual review writing, manuscript revision. For evaluating…
scientific-critical-thinking
Evaluate scientific claims and evidence quality. Use for assessing experimental design validity, identifying biases and confounders, applying evidence grading frameworks (GRADE, Cochrane Risk of Bias), or teaching critical analysis. Best for understanding evidence quality, identifying flaws. For formal peer review…
statistical-analysis
Guided statistical analysis for research data - test selection, assumption checking, effect sizes, power analysis, Bayesian alternatives, and APA-formatted reporting. Use whenever a user wants to compare groups, test a hypothesis, analyze experimental or survey data, check statistical assumptions, compute required…
statistical-power
Sample-size and statistical power calculations for planning studies. Use whenever someone asks "how many subjects/samples/replicates do I need", wants an a priori power analysis, a minimum detectable effect (MDE), a power curve, or needs to justify a sample size for a grant, IRB protocol, or pre-registration. Covers…
pr-integration-test
Design, implement, and validate Intelligent Terminal integration tests for a target pull request or regression. Use when asked to add PR integration tests, convert a bug fix into E2E coverage, prove existing behavior still works, map tests to the release checklist, or verify E2E reports mark checklist cases complete.