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 jxoesneon/Ciel --skill secrets_managergit clone --depth 1 https://github.com/jxoesneon/CielWrote 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/jxoesneon/ciel/secrets_manager)<a href="https://agentmods.dev/skills/jxoesneon/ciel/secrets_manager"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/secrets_manager.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.00020 | $0.00321 |
| Opus 5 | $0.00010 | $0.00161 |
| Sonnet 5 | $0.00004 | $0.00064 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
secrets_manager 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 6d 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
secrets_manager
Resolve credentials by reference; never inline.
Operations
sec.get(ref)— returns a handle (opaque token). Handles are single-use by default.sec.redact(text)— scrub secret patterns.sec.list_sources()— env, keychain, vault types available.sec.set(ref, source=keychain|env)— store (never plaintext in files).
I/O Contract
io_contract:
input: { op, ref, "args?" }
output: { handle_or_ok }
idempotent: depends
side_effects: [keychain]
Constraints (Constitutional)
- Raw secrets never touch activity.log, MemPalace, Council artifacts, or git.
sec.redactruns at capture time on stdout/stderr flowing to storage.- Refusal to exfiltrate: any operation that would transmit a secret to a network endpoint requires critical-risk escalation.
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.
- 6d ago First seen · 39 lines · 20 tokens per session scan A 0d3aa990b9fa
secrets_manager is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 6d ago), licensed Apache-2.0. It adds 20 tokens to every session and 321 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-31.
Other skills, from other repositories
ticket-spec
Turn a raw Linear Triage ticket into a fully specified ai:agent-ready one by exploring the codebase. Use when specifying, refining, or promoting tickets, or when asked why a ticket isn't dispatchable.
redpolicy-guide
An editorial policy for turning webinar transcripts into self-contained guides. A transcript is a written record of spoken material, while a self-contained guide can be understood without watching the webinar.
Code Quality Review
Conduct a comprehensive code quality review focused on clean code, architecture, and project standards.
write-overview
A workflow for researching and writing a review essay about a project topic when no finished source text exists. It gathers the facts, studies example essays when available and produces the article in a project output folder.
redpolicy-article
An editorial guide for writing comparison articles about services, tools, and products. It defines a consistent entry format covering the name, link, price, description, and notable features.
surge
Use when a user provides a PRD, spec, or detailed requirements document and needs a full project delivered through iterative expert orchestration — multi-round analyze/research/design/implement/QA cycles with convergence detection. NOT for: single-file edits, quick prototypes, simple Q&A, or tasks without a written…