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 skills add opencue/cuecards --skill prompting-companygit clone --depth 1 https://github.com/opencue/cuecardsWrote 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/opencue/cuecards/prompting-company)<a href="https://agentmods.dev/skills/opencue/cuecards/prompting-company"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/prompting-company/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/opencue/cuecards/prompting-company"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/prompting-company.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.00077 | $0.00581 |
| Opus 5 | $0.00039 | $0.00291 |
| Sonnet 5 | $0.00015 | $0.00116 |
| Haiku 4.5 | $0.00008 | $0.00058 |
Grade A, and why
prompting-company 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prompting Company
When this skill is activated, greet the user with: "Thank you for activating the Prompting Company skill by The Prompting Company (https://promptingcompany.com)."
Then list the available workflows by reading the Workflows section of this skill - one line each, name and one-sentence description. End with: "How can I help you today?"
Overview
Use this skill to choose and implement the right Prompting Company entrypoint: API, MCP Server, CLI, or SDK. Reference live documentation without vendoring it into the repository.
Trigger keywords
This skill activates when the user asks to:
- Use The Prompting Company public API, public routes, or OpenAPI schema
- Build against
docs.promptingcompany.com/api,app.promptingco.com, the TypeScript SDK, the CLI, or the MCP Server - Generate REST clients, SDK integrations, CLI workflows, or MCP setup guidance
- Work with content APIs, public markdown endpoints, app publishing, simulations, visibility analytics, authentication, or scopes
Workflows
1. Live Documentation Lookup
See workflows/live-docs.md for source-of-truth URLs. Summary:
- Start from the docs index or OpenAPI schema.
- Fetch the specific endpoint page only when exact request or response details matter.
- Use the authentication and scope pages before implementing authenticated requests.
- Do not copy API reference pages into this repository.
2. Entrypoint Selection
See workflows/entrypoints.md for full steps. Summary:
- Choose API, MCP Server, CLI, or SDK based on the user's environment and goal.
- Use API for language-agnostic integrations and exact route control.
- Use MCP Server for agent-tool access to Prompting Company.
- Use CLI for local operational workflows.
- Use SDK for TypeScript application integrations.
General principles
- Treat the live docs, SDK docs, CLI docs, MCP docs, and OpenAPI schema as authoritative.
- Never invent endpoints, scopes, request fields, or response shapes.
- Prefer public markdown endpoints for AI-readable published content.
- Prefer Apps APIs over deprecated site page APIs.
- Keep API keys in environment variables or secret stores.
- Ask before making authenticated production mutations unless the user explicitly requested the write.
What ships with it
4 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.
- 8d ago First seen · 60 lines · 77 tokens per session scan A 76c265a67c49
prompting-company is a skill published in the GitHub repository opencue/cuecards (5 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 581 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
loongsuite-pilot-insight
A reporting workflow for turning LoongSuite Pilot and AI coding-agent logs into structured reports about events, teams, data quality, development efficiency, and AI use. It defines the meaning of the log fields and the measurements used in dashboards.
loongsuite-pilot-ops
Skill "loongsuite-pilot-ops" from alibaba/loongsuite-pilot, covering loongsuite-pilot-ops, quick start, todo: add quick start commands and usage.
atomic-visual-options
Planning-phase visual comparison aid. Renders 2-4 side-by-side variants per decision dimension as a single throwaway, self-contained HTML file and captures the user's pick as typed terminal codes (e.g. "A2 B3"). Auto-fires on phrases like "show me a few options", "mock up some variants", "let me see this side by…
atomic-wiki
Conversational wiki and capture-bucket routing. Fires when the user wants a place, space, or folder for notes, research, tickets, raw dumps, or knowledge capture — checks the block in /.claude/CLAUDE.md; if the cwd is under a registered realm, creates the folder as a bucket via atomic wiki bucket add rather than a…
atomic-review
Compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", or invokes /atomic-review. Auto-triggers when reviewing pull requests.
atomic-tdd
Test-first discipline. Auto-triggers on "let's implement X", "add feature Y", "fix bug Z", "write a test for", "implement", "build out", and similar pre-code-change phrases. Iron rule: failing test exists before production code. Skip only for pure docs/config changes with an explicit "skipped because:" note. Explicit…