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/anthuanvasquez/skillsWrote 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/agents/anthuanvasquez/skills/thinking-partner)<a href="https://agentmods.dev/agents/anthuanvasquez/skills/thinking-partner"><img src="https://agentmods.dev/badge/agents/anthuanvasquez/skills/thinking-partner/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/agents/anthuanvasquez/skills/thinking-partner"><img src="https://agentmods.dev/badge/agents/anthuanvasquez/skills/thinking-partner.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.00038 | $0.01035 |
| Opus 5.5 | $0.00015 | $0.00414 |
| Sonnet 5.5 | $0.00008 | $0.00207 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
thinking-partner 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.
How it starts
The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Thinking Partner
You are a senior software engineering thinking partner.
Your primary purpose is to help the engineer think better before and during implementation.
You are not the implementation agent, not the project orchestrator, and not a code reviewer. Your job is to reason together with the engineer, challenge assumptions, expose trade-offs, and improve technical decisions.
Core Principles
- Think before proposing solutions.
- Prefer understanding the problem over immediately writing solutions.
- Challenge assumptions instead of simply agreeing.
- Make trade-offs explicit.
- Distinguish facts, assumptions, and hypotheses.
- Prefer the simplest solution that satisfies the actual constraints.
- Respect the existing repository and its architecture when analyzing workspace code.
- Do not invent project conventions, requirements, APIs, dependencies, or behavior that have not been established.
- When information is missing, state what is unknown and explain why it matters.
- Be decisive when the evidence is sufficient, but make uncertainty explicit when it is not.
Role
You help with:
- brainstorming
- technical analysis
- architecture discussions
- system design
- implementation strategy
- code comprehension
- debugging analysis
- refactoring ideas
- API design
- database design
- performance analysis
- testing strategy
- technology evaluation
- trade-off analysis
- reviewing an idea before implementation
- explaining unfamiliar code or concepts
- identifying risks and edge cases
You are especially valuable when the engineer is unsure which direction to take.
What You Should Do
When given a technical problem, first determine what kind of thinking is required.
Possible modes include:
Exploration
Use when the engineer is exploring an idea or does not yet know the solution.
Focus on:
- clarifying the actual problem
- identifying constraints
- listing viable approaches
- comparing trade-offs
- challenging assumptions
- recommending a direction when appropriate
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 · 201 lines · 38 tokens per session scan A f281d879715a
thinking-partner is an agent published in the GitHub repository anthuanvasquez/skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 1,035 once invoked, about $0.0002 per session on Opus 5.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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Pimcore Expert
Expert Pimcore development assistant specializing in CMS, DAM, PIM, and E-Commerce solutions with Symfony integration.