use-shared-credential

use-shared-credential is a skill for Claude Code, Codex from yc-software/qm. It costs 87 tokens per session (1,096 once invoked), scanned A, original, MIT.

Instructions for calling an external service through an organization-managed credential broker. The broker adds the shared secret to an approved request without showing the secret to the agent.

In plain words
What is it for?
Use it when an organization provides a shared search key, paid API key, data feed, or Git credential and the service must be contacted through the broker.
Why use it?
Shared API keys and other credentials can be exposed if copied into the agent's environment or conversation. Proxying keeps the secret hidden while allowing approved requests.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/yc-software/qm/use-shared-credential
Any agent
npx skills add yc-software/qm --skill use-shared-credential
Clone the repo
git clone --depth 1 https://github.com/yc-software/qm

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for use-shared-credential

README.md
[![agentmods](https://agentmods.dev/badge/skills/yc-software/qm/use-shared-credential.svg)](https://agentmods.dev/skills/yc-software/qm/use-shared-credential)
Your own site
<a href="https://agentmods.dev/skills/yc-software/qm/use-shared-credential"><img src="https://agentmods.dev/badge/skills/yc-software/qm/use-shared-credential.svg" alt="Measured on agentmods" height="20"></a>
Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,096 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00087 $0.01096
Opus 5 $0.00044 $0.00548
Sonnet 5 $0.00017 $0.00219
Haiku 4.5 $0.00009 $0.00110

Measured 4d ago against content hash 2893e1f3efe8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

use-shared-credential scanned grade A with 1 finding 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 4d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -fsS -X POST "$AGENT_API_URL/v1/credentials/broker" \
skills-seed/use-shared-credential/SKILL.md · 90 lines

How it starts

The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Use a shared org credential (by proxy, never the raw secret)

Some credentials aren't yours and aren't on your computer — they're one org credential the admin vends to people, like a shared doc: an org web-search key, a paid-API key, a data-vendor feed. You are NOT given the secret (a shared bearer sitting in your shell could leak). Instead you make the call by proxy: you name the credential + the request, and the core stamps the secret onto the outbound call at the wire and returns the response.

When this applies

Your system prompt lists, under "Shared org credentials available to you", any credentials vended to this conversation — each with its slug, host, and the methods/paths you may use. If that section is absent (or your environment has no AGENT_CREDENTIAL_TOKEN), you have none — do not try to reach those services another way, and don't ask the user to paste a token.

How to call it

curl -fsS -X POST "$AGENT_API_URL/v1/credentials/broker" \
  -H "x-agent-capability: $AGENT_CREDENTIAL_TOKEN" \
  -H "content-type: application/json" \
  -d '{
        "credential": "<slug from your system prompt>",
        "method": "GET",
        "url": "https://<the credential's host>/<allowed path>?<query>",
        "headers": { "accept": "application/json" }
      }'

The reply is an envelope — the upstream status + body, never the secret:

{ "status": 200, "contentType": "application/json", "body": "<the upstream response text>" }

Parse body as the upstream returned it (e.g. JSON). For a write (when the credential allows a non-GET method), put the request payload in the body field of your POST.

Git smart HTTP remotes

Some shared credentials are for Git remotes, where git clone, git fetch, and git push speak Git's smart HTTP protocol instead of JSON REST. Do not put the upstream token in a clone URL. Use the core-hosted remote path instead:

git remote add broker "$AGENT_API_URL/v1/credentials/git/<slug>/<repo-path>.git"
git -c http.extraHeader="x-agent-capability: $AGENT_CREDENTIAL_TOKEN" \
  push broker HEAD:refs/heads/codex/small-change

Read the full file on GitHub · 90 lines

Changes

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.

  1. 4d ago First seen · 90 lines · 87 tokens per session scan A 2893e1f3efe8

Subscribe to this mod's changes

use-shared-credential is a skill published in the GitHub repository yc-software/qm (14,533 stars, last pushed today), licensed MIT. It adds 87 tokens to every session and 1,096 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

open-code-review

Performs AI-powered code review on Git changes using the ocr CLI from alibaba/open-code-review. Use when the user asks to review code, review a pull request, review staged/unstaged changes, review a commit, or compare branches for code quality issues. Produces line-level review comments and can automatically apply…

alibaba/open-code-review · 98 tokens

adding-a-provider-api-feature

Add a new provider API capability (prompt caching, strict/structured tool calling, thinking/reasoning effort, service tier, safety settings, logprobs, etc.) to Pydantic AI. Use when wiring a provider feature through the library — it enforces reasoning from the existing cross-provider abstraction before designing…

pydantic/pydantic-ai · 97 tokens

agent-initialization

Initialize an Agent's settings from a user requirement by writing AGENTS.md, setting identity metadata, and installing only needed Skills.

Prism-Shadow/penguin-harness · 30 tokens

openclaw-ci-limits

Manage OpenClaw GitHub Actions and Blacksmith CI capacity, runner-registration budgets, fanout caps, main-push single-flight, shard sizing, hosted-runner offload, queue health, and safe ramp-down/ramp-up changes. Use when tuning .github/workflows/, docs/ci.md, CI runner labels, matrix max-parallel…

openclaw/openclaw · 105 tokens

release-openclaw-plugin-testing

Plan and run pre-release OpenClaw plugin validation across bundled plugins, package artifacts, lifecycle commands, doctor/fix, config round-trip, gateway startup, SDK compatibility, Docker E2E, Package Acceptance, and Testbox proof.

openclaw/openclaw · 54 tokens

portfolio

Cross-chain DeFi portfolio discovery, rebalancing suggestions, and NEAR Intent construction. Activates when the user pastes a wallet address or asks about yield/positions/rebalancing. Bootstraps a per-user "portfolio" project, aggregates positions across all the user's addresses inside one project, and offers a…

suyoumo/ClawProBench · 69 tokens