Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add staqsIO/terminalhire-plugin/plugin install terminalhireWrote 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/staqsio/terminalhire-plugin/connect)<a href="https://agentmods.dev/skills/staqsio/terminalhire-plugin/connect"><img src="https://agentmods.dev/badge/skills/staqsio/terminalhire-plugin/connect.svg" alt="Measured on agentmods" 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.00064 | $0.00600 |
| Opus 5 | $0.00032 | $0.00300 |
| Sonnet 5 | $0.00013 | $0.00120 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
connect 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 8d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
terminalhire:connect
Privacy-preserving dev↔dev / founder↔builder connection: discover opted-in people matched to your work using a profile that never leaves your machine, then exchange contact only through a double-opt-in intro. No profile data is ever sent for matching — only an intro you explicitly approve crosses the wire.
Discover people & projects
Rank opted-in developers (and founders' projects) against a profile that never leaves your machine:
node "${CLAUDE_PLUGIN_ROOT}/dist/bin/jpi-dispatch.js" devs
Each result shows the person/project, a match score, the "why matched" tags, and a verifiable /r/<login> credential link. The directory is downloaded anonymously; your profile never leaves your machine.
Founder side — staff a project
Declare a project — it never leaves your machine — then rank builders for it:
node "${CLAUDE_PLUGIN_ROOT}/dist/bin/jpi-dispatch.js" project "Shopify analytics app: react, typescript, postgres"
node "${CLAUDE_PLUGIN_ROOT}/dist/bin/jpi-dispatch.js" devs --as-project
Request a connection (double-opt-in)
Request a consented intro to someone you matched with:
node "${CLAUDE_PLUGIN_ROOT}/dist/bin/jpi-dispatch.js" intro <github-login>
A typed-yes gate shows exactly what crosses the wire (your login + chosen display name + chosen contact + optional note). The target is emailed with only your public login — no contact is shared until they accept.
Accept or review incoming requests:
node "${CLAUDE_PLUGIN_ROOT}/dist/bin/jpi-dispatch.js" intro --list # pending intros
node "${CLAUDE_PLUGIN_ROOT}/dist/bin/jpi-dispatch.js" intro --accept <id> # accept → contacts exchanged
Contacts are exchanged only on mutual accept; declining exchanges nothing, and either party can delete an intro at any time.
To appear in the directory yourself, publish your résumé (
resume_public) from the dashboard — only opted-in developers are discoverable.
Note: invoke the plugin-bundled engine via
${CLAUDE_PLUGIN_ROOT}so a plugin update is the only update needed (no separatenpmstep). If$CLAUDE_PLUGIN_ROOTis unset — e.g. running outside Claude Code — fall back to the standalone commandsterminalhire devs/terminalhire project/terminalhire intro.
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.
- 8d ago First seen · 51 lines · 64 tokens per session scan A 38ac45aa120b
connect is a skill published in the GitHub repository staqsIO/terminalhire-plugin (2 stars, last pushed 5d ago), licensed MIT. It adds 64 tokens to every session and 600 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…