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 Ghosteken/agent-harness --skill azure-keyvault-secrets-rustgit clone --depth 1 https://github.com/Ghosteken/agent-harnessWrote 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/ghosteken/agent-harness/azure-keyvault-secrets-rust)<a href="https://agentmods.dev/skills/ghosteken/agent-harness/azure-keyvault-secrets-rust"><img src="https://agentmods.dev/badge/skills/ghosteken/agent-harness/azure-keyvault-secrets-rust/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/ghosteken/agent-harness/azure-keyvault-secrets-rust"><img src="https://agentmods.dev/badge/skills/ghosteken/agent-harness/azure-keyvault-secrets-rust.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.00053 | $0.00926 |
| Opus 5.5 | $0.00021 | $0.00370 |
| Sonnet 5.5 | $0.00011 | $0.00185 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade A, and why
azure-keyvault-secrets-rust 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 1mo 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.
This is a copy
89% identical to azure-keyvault-secrets-rust — 11 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Key Vault Secrets SDK for Rust
Client library for Azure Key Vault Secrets — secure storage for passwords, API keys, and other secrets.
Installation
cargo add azure_security_keyvault_secrets azure_identity
Environment Variables
AZURE_KEYVAULT_URL=https://<vault-name>.vault.azure.net/
Authentication
use azure_identity::DeveloperToolsCredential;
use azure_security_keyvault_secrets::SecretClient;
let credential = DeveloperToolsCredential::new(None)?;
let client = SecretClient::new(
"https://<vault-name>.vault.azure.net/",
credential.clone(),
None,
)?;
Core Operations
Get Secret
let secret = client
.get_secret("secret-name", None)
.await?
.into_model()?;
println!("Secret value: {:?}", secret.value);
Set Secret
use azure_security_keyvault_secrets::models::SetSecretParameters;
let params = SetSecretParameters {
value: Some("secret-value".into()),
..Default::default()
};
let secret = client
.set_secret("secret-name", params.try_into()?, None)
.await?
.into_model()?;
Update Secret Properties
use azure_security_keyvault_secrets::models::UpdateSecretPropertiesParameters;
use std::collections::HashMap;
let params = UpdateSecretPropertiesParameters {
content_type: Some("text/plain".into()),
tags: Some(HashMap::from([("env".into(), "prod".into())])),
..Default::default()
};
client
.update_secret_properties("secret-name", params.try_into()?, None)
.await?;
Delete Secret
client.delete_secret("secret-name", None).await?;
List Secrets
use azure_security_keyvault_secrets::ResourceExt;
use futures::TryStreamExt;
let mut pager = client.list_secret_properties(None)?.into_stream();
while let Some(secret) = pager.try_next().await? {
let name = secret.resource_id()?.name;
println!("Secret: {}", name);
}
Get Specific Version
use azure_security_keyvault_secrets::models::SecretClientGetSecretOptions;
let options = SecretClientGetSecretOptions {
secret_version: Some("version-id".into()),
..Default::default()
};
let secret = client
.get_secret("secret-name", Some(options))
.await?
.into_model()?;
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.
- 1mo ago First seen · 151 lines · 53 tokens per session scan A 53b78d4f1107
azure-keyvault-secrets-rust is a skill published in the GitHub repository Ghosteken/agent-harness (4 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 926 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to azure-keyvault-secrets-rust, differing in 11 lines, and is treated as a copy.
Other skills, from other repositories
rust-check
Run cargo check on the current Rust project to find compile errors.
Rust Standards
Complete Rust coding, linting, testing, architecture, and layer boundary standards for systemprompt.io development.
agentic-infrastructure-2026
Build and adopt production AI agent infrastructure in 2026. Covers framework selection (LangGraph, CrewAI, AutoGen, MCP), orchestration patterns, evaluation, observability, memory systems, and tool use. Also covers the SOCIAL dimension: how to sell agent infrastructure internally, change management, measuring ROI…
rust-performance
Use when writing or reviewing performance-sensitive Rust, profiling slow Rust code, reducing allocations, investigating latency or throughput regressions, or diagnosing bloated binaries and long compile times. Covers allocation, iterators, data layout, hashing, async/concurrency, build profiles, Clippy review gates…
rust-unsafe-ffi
Use when writing or reviewing Rust unsafe blocks, raw-pointer abstractions, MaybeUninit or manual Drop code, unsafe trait implementations, or C/C++ FFI bindings. Covers pointer validity, aliasing and provenance, C ABI/layout, callbacks, allocator ownership, C strings, unwinding, Rust 2024 unsafe syntax, and…
rust-algorithms
Use when choosing Rust collections or implementing and reviewing algorithmic solutions: two pointers, sliding windows, binary search, prefix sums, monotonic stacks, hash maps, streaming medians, intervals, cyclic sort, BFS/DFS, backtracking, dynamic programming, greedy algorithms, topological sort, union-find, tries…