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 orchestra-hq/orchestra-skills --skill prefect-secrets-to-orchestragit clone --depth 1 https://github.com/orchestra-hq/orchestra-skillsWrote 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/orchestra-hq/orchestra-skills/prefect-secrets-to-orchestra)<a href="https://agentmods.dev/skills/orchestra-hq/orchestra-skills/prefect-secrets-to-orchestra"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/prefect-secrets-to-orchestra/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/orchestra-hq/orchestra-skills/prefect-secrets-to-orchestra"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/prefect-secrets-to-orchestra.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.00086 | $0.01587 |
| Opus 5 | $0.00043 | $0.00794 |
| Sonnet 5 | $0.00017 | $0.00317 |
| Haiku 4.5 | $0.00009 | $0.00159 |
Grade A, and why
prefect-secrets-to-orchestra 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 12d 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.
response = requests.get("https://api.example.com/data", headers={"Authorization": f"Bearer {token}"}) How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
This skill produces a secrets checklist — a table of every secret name, where it came from in Prefect, and where it must be re-entered in Orchestra. It never asks for actual secret values and never writes them to any file. Prefect's encrypted Secret block store has no bulk export mechanism; every secret must be re-entered by hand in Orchestra.
Parameter Mapping
| Prefect secret pattern | Orchestra target | Notes |
|---|---|---|
Secret.load("api-key").get() for a SaaS credential |
Store on that tool's Orchestra connection credential field | Use prefect-connections-to-orchestra to identify the connection |
SecretStr field on a credential block |
Store on Orchestra connection credential field | Follow prefect-connections-to-orchestra for the block type |
Secret value used inside a @task as an env var |
Python connection → env var → read via os.getenv("KEY") in script |
|
SecretDict |
Multiple key-value entries on the relevant connection | One Orchestra field per key |
AwsSecret / AWS Secrets Manager block |
Orchestra AWS Secrets Manager credential store | Create an Orchestra AWS connection; secret JSON keys must match the target integration's expected fields |
Prefect Variables (non-sensitive, Variable.get()) |
Pipeline inputs: or task env_vars: — not secrets |
Variables are not encrypted; treat as config, not credentials |
Hard rule (enforced always):
NEVER ask the user to paste real secret values into this chat, and never write real secret values into any file. Produce only a checklist of secret NAMES and where to enter them.
Orchestra YAML Structure
Secrets themselves do not appear in YAML. The YAML only shows where the secret will be consumed:
# Python task reading a secret from env var (set on the connection)
integration: PYTHON
integration_job: PYTHON_EXECUTE_SCRIPT
connection: python_git_prod_12345 # env vars set on this connection in Orchestra UI
parameters:
command: 'python scripts/call_api.py'
python_version: '3.12'
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.
- 12d ago First seen · 137 lines · 86 tokens per session scan A c1674f2cf9ce
prefect-secrets-to-orchestra is a skill published in the GitHub repository orchestra-hq/orchestra-skills (9 stars, last pushed 3d ago), licensed MIT. It adds 86 tokens to every session and 1,587 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-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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…