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/freibergergarcia/phone-a-friendWrote 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/commands/freibergergarcia/phone-a-friend/curiosity-engine)<a href="https://agentmods.dev/commands/freibergergarcia/phone-a-friend/curiosity-engine"><img src="https://agentmods.dev/badge/commands/freibergergarcia/phone-a-friend/curiosity-engine/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/commands/freibergergarcia/phone-a-friend/curiosity-engine"><img src="https://agentmods.dev/badge/commands/freibergergarcia/phone-a-friend/curiosity-engine.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.00041 | $0.04242 |
| Opus 5 | $0.00020 | $0.02121 |
| Sonnet 5 | $0.00008 | $0.00848 |
| Haiku 4.5 | $0.00004 | $0.00424 |
Grade B, and why
curiosity-engine scanned grade B with 2 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 10d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
| **Ollama** | `PROMPT_JSON="$(jq -Rs . < "$PROMPT_FILE")"; curl -s http://localhost:11434/api/chat -H "Content-Type: application/json" -d "{\"model\":\"<model>\",\"messages\":[{\"role\":\"user\",\"content\":${PROMPT_JSO Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| **Ollama** | `PROMPT_JSON="$(jq -Rs . < "$PROMPT_FILE")"; curl -s http://localhost:11434/api/chat -H "Content-Type: application/json" -d "{\"model\":\"<model>\",\"messages\":[{\"role\":\"user\",\"content\":${PROMPT_JSO How it starts
The opening of the file, as written. The whole thing — 412 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/curiosity-engine
A structured ping-pong Q&A game between the host orchestrating model (the agent running this skill — Claude in Claude Code, the OpenCode model in OpenCode) and a backend model. Both sides MUST produce an ANSWER: and a QUESTION: every round. The game is seeded with a topic and runs for N rounds (default 3, max 6).
Execution rules
- The host model running this skill is the orchestrator. It serves the
opening question and answers each round directly. Do NOT call
phone-a-friend --to claude(or any other backend) to generate the orchestrator's questions or answers — that would relay the orchestrator role to a different model. - One backend per relay call. Never pass comma-separated values to
--to(e.g.phone-a-friend --to codex,gemini). curiosity-engineis a host slash command / Agent Skill, not a PaF CLI subcommand. Never runphone-a-friend curiosity-engine.--backendis an argument to this skill, not a PaF CLI flag. Do not pass--backendtophone-a-friend.- Suppress the working-tree diff on every binary-mode relay (see "Diff suppression" below). Curiosity rounds are seeded with self-contained prompts; the diff would be noise.
- Do NOT dump repo files or git output (
git show,git diff,git status, etc.) into the relay prompt. Curiosity rounds are seeded with self-contained prompts; if the round needs file context, repo-aware backends (antigravity, codex, gemini) can read the repo via--repo "$PWD". Forollama(no repo file access), pick a repo-aware backend instead, or ask before sending a minimal excerpt. Inlining repo content can leak uncommitted edits or committed secrets and is not needed for a Q&A rally. The opening question and round transcripts are narrative context that the orchestrator generates and inlines into the relay prompt; that is the intended use, not file dumping.
Inputs
- Arguments:
$ARGUMENTS
Step 0 — Relay mode
command -v phone-a-friend
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.
- 10d ago First seen · 412 lines · 41 tokens per session scan B b5e7e8c153ab
curiosity-engine is a command published in the GitHub repository freibergergarcia/phone-a-friend (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 41 tokens to every session and 4,242 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
atomic-plan
Write a design doc (concepts, business rules, approaches) and a checkpoint-table spec (contract) for non-trivial work; inline spec only for trivial. Gauges triviality; loops spec authoring with subagents. Human-facing artifact, Mermaid diagrams allowed.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
Stage, commit, and optionally ship further. Pass an escalation token (push, pr, merge, squash, squash merge) to skip the prompt. With no token, commits then asks how far to ship. Delegates message format to the atomic-git-discipline skill.
create-task-list.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
adopt-roadmap.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.