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 commands/pipefy/ai-toolkit/pipefy-logingit clone --depth 1 https://github.com/pipefy/ai-toolkitWrote 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/pipefy/ai-toolkit/pipefy-login)<a href="https://agentmods.dev/commands/pipefy/ai-toolkit/pipefy-login"><img src="https://agentmods.dev/badge/commands/pipefy/ai-toolkit/pipefy-login.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 | $0.00020 | $0.00152 |
| Opus 5 | $0.00010 | $0.00076 |
| Sonnet 5 | $0.00004 | $0.00030 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
pipefy-login 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 3d 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
If command -v pipefy fails, stop and tell the user to run /pipefy:install first.
Otherwise prompt the user to confirm running:
pipefy auth login $ARGUMENTS
This targets Pipefy production by default. Only set PIPEFY_AUTH_URL (the OIDC issuer URL) in the shell environment when logging in to a non-prod IdP; it defaults to https://signin.pipefy.com/realms/pipefy.
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.
- 3d ago First seen · 17 lines · 20 tokens per session scan A 69c296a2b979
pipefy-login is a command published in the GitHub repository pipefy/ai-toolkit (44 stars, last pushed 7d ago), licensed Apache-2.0. It adds 20 tokens to every session and 152 once invoked, about $0.0001 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 commands, from other repositories
create-skill
Create a new skill via GitHub search, LLM generation, or both.
suggest-skills
Identify gaps in your skill library and suggest new skills to create based on project context.
sync-all
Sync skills, commands, MCP servers, and preferences between Claude, Codex, Copilot, and Cursor in one operation.
sync-from-claude
Sync skills from Claude Code (/.claude) into Codex, Cursor, or Copilot.
sync-from-cursor
Sync skills, commands, agents, hooks, rules, and MCP from Cursor IDE to Claude, Codex, or Copilot.
sync-to-cursor
Sync skills, commands, agents, hooks, rules, and MCP from Claude, Codex, or Copilot to Cursor IDE.