Borrowing it
Nothing to install: this file belongs to ineersa/re-search. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ineersa/re-search/main/.cursor/skills/mate-tools/SKILL.mdgit clone --depth 1 https://github.com/ineersa/re-searchWrote 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/skills/ineersa/re-search/mate-tools)<a href="https://agentmods.dev/skills/ineersa/re-search/mate-tools"><img src="https://agentmods.dev/badge/skills/ineersa/re-search/mate-tools/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/skills/ineersa/re-search/mate-tools"><img src="https://agentmods.dev/badge/skills/ineersa/re-search/mate-tools.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.00056 | $0.01268 |
| Opus 5.5 | $0.00022 | $0.00507 |
| Sonnet 5.5 | $0.00011 | $0.00254 |
| Haiku 4.5 | $0.00006 | $0.00127 |
Grade A, and why
mate-tools 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 2mo 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mate Tools
Use this skill when working with Symfony AI Mate capabilities in this repository: static analysis, test execution, logs, Symfony service/profiler inspection, and runtime introspection.
This project runs Mate from the Docker php service. Tool execution should therefore mirror container runtime behavior, not host PHP behavior.
When to use
- User asks to run or explain Mate tools.
- User needs schema/parameters for
phpstan,phpunit,monolog, or Symfony profiler tools. - User wants CLI equivalents for MCP tool calls.
- User needs repeatable Docker-safe commands for Mate operations.
Required: ALWAYS use the wrapper script
MANDATORY: All Mate MCP tool invocations MUST use the provided wrapper script:
.cursor/skills/mate-tools/scripts/mate-tool-call.sh <tool-name> '<json-input>'
NEVER call docker compose exec ... vendor/bin/mate directly. The wrapper ensures:
- Correct Docker container context (PHP 8.5 runtime)
- TOON format output for LLM efficiency
- Proper stderr suppression of bootstrap noise
- Consistent environment across all tool calls
Why this wrapper exists
- Keeps all tool calls inside the
phpcontainer. - Avoids repeating long commands.
- Standardizes TOON output format for LLM efficiency.
Usage
<tool-name>: Mate MCP tool name, e.g.server-info,phpstan-analyse.<json-input>: JSON object string, e.g.'{}','{"mode":"summary"}'.
Run from repo root (where compose.yaml lives). JSON must be valid. Use single quotes around the JSON string in shell. If Docker stack is down, start it first (make up).
Discovering available tools
docker compose exec -T php php vendor/bin/mate mcp:tools:list --format=toon
Debugging
- Wrapper hides Mate bootstrap
[INFO]lines by default by redirecting stderr. - To keep bootstrap logs visible:
MATE_TOOL_CALL_SHOW_BOOT_LOGS=1 .cursor/skills/mate-tools/scripts/mate-tool-call.sh ....
Operating rules
- ALWAYS use the wrapper script for all Mate tool calls.
- Prefer Mate MCP tools for focused diagnostics and machine-readable output.
- All tool output uses
--format=toonfor maximum token efficiency in LLM contexts. - Use concise modes first (
summary/default), then increase detail only when needed. - For direct shell-based quality tasks in this repo, follow project policy and prefer
maketargets. - Keep JSON input explicit and valid; pass
{}when a tool expects an object with no required fields.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 134 lines · 56 tokens per session scan A 448285c4fe25
mate-tools is a skill published in the GitHub repository ineersa/re-search (5 stars, last pushed 7mo ago), licensed MIT. It adds 56 tokens to every session and 1,268 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 skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
observability-langsmith
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
reenable-test
Guide for investigating, fixing, verifying via TDD, and re-enabling disabled or flaky Chromium tests (C++, Android Java, or WebUI). Use this skill when asked to deflake, fix, or re-enable a disabled or flaky test case, or to verify post-submit stability of a re-enabled test. Don't use for disabling a failing test…
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.