agentmods.dev

tenuo-denial-triage

tenuo-denial-triage is a skill for Claude Code, Codex from tenuo-ai/tenuo. It costs 111 tokens per session (2,046 once invoked), scanned A, original, Apache-2.0.

A troubleshooting workflow for a denied Tenuo call, test, or agent step. It finds whether the caller, policy, or configuration caused the denial and applies the smallest legitimate authority change.

In plain words
What is it for?
Use it to investigate Tenuo denials involving authority, proofs, chains, expiry, approvals, or unknown arguments, then make the permitted call work.
Why use it?
It helps fix permission errors without bypassing the verifier or giving an agent broader access than necessary. It also preserves the exact error and examines the decision point that rejected the call.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 103repo today A scan 111 tokens original Apache-2.0

Good fit Use it to investigate Tenuo denials involving authority, proofs, chains, expiry, approvals, or unknown arguments, then make the permitted call work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tenuo-ai/tenuo/tenuo-denial-triage
View source ↗ tenuo-ai/tenuo tenuo.ai
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.

Any agent
npx skills add tenuo-ai/tenuo --skill tenuo-denial-triage
Clone the repo
git clone --depth 1 https://github.com/tenuo-ai/tenuo

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 tenuo-denial-triage

README.md
[![agentmods](https://agentmods.dev/badge/skills/tenuo-ai/tenuo/tenuo-denial-triage/github.svg)](https://agentmods.dev/skills/tenuo-ai/tenuo/tenuo-denial-triage)
Your own site
<a href="https://agentmods.dev/skills/tenuo-ai/tenuo/tenuo-denial-triage"><img src="https://agentmods.dev/badge/skills/tenuo-ai/tenuo/tenuo-denial-triage/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.

agentmods 80×15 button for tenuo-denial-triage

Your own site · 80×15
<a href="https://agentmods.dev/skills/tenuo-ai/tenuo/tenuo-denial-triage"><img src="https://agentmods.dev/badge/skills/tenuo-ai/tenuo/tenuo-denial-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 111 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,046 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00111 $0.02046
Opus 5.5 $0.00044 $0.00818
Sonnet 5.5 $0.00022 $0.00409
Haiku 4.5 $0.00011 $0.00205

Measured 19d ago against content hash b772a621e015, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

tenuo-denial-triage 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 19d 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.

skills/tenuo-denial-triage/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.

Tenuo Denial Triage

A denial is the system working. Find out whether the caller, the policy, or the configuration is wrong, then fix that with the smallest possible increase in authority. Never route around the verifier, and never make a test pass by widening what the agent may do.

Announce at start: "I'm using the tenuo-denial-triage skill to find why this call was denied and the narrowest fix."

Collect the facts before changing anything

  1. The exact error. Class or code, message, hint, and the field or tool it names. Keep the text; do not paraphrase it away.
  2. The decision point. Which verifier denied: an in-process guard, an MCP server, a gateway, a sidecar, a worker. And which link: root trust, an intermediate warrant, the leaf, the proof-of-possession, or an approval gate.
  3. The presented authority, from the SDK's own diagnostics, not from reading code. In Python, why_denied() on the warrant for the exact tool and arguments, diagnose() on the warrant, explain() on the caught error, and info() for configuration. In TypeScript, session.inspect() and tenuo.explain(session, tool, args). In Rust, the Diagnostics helper's explain_denial, why_denied, and explain_authority. From a shell, tenuo inspect and tenuo verify. When the denial happened in another process, start from the receipt: its decision code, action, request hash, and trusted-roots hash say what the verifier saw. Confirm every diagnostic name against the installed package version before relying on it.
  4. The call as the verifier saw it. Tool name, every argument after normalization and injection, the holder key that signed, and the timestamp. Argument names and types matter as much as values.

Write a one-screen triage note before editing:

Error:          <class or code>: <message>
Denied check:   tool | constraint(<field>) | unknown field | expiry | PoP | chain | monotonicity | revocation | approval | configuration
Decision point: <component> at <file:line or service>, chain link: <root | intermediate | leaf | PoP>
Presented:      tools=<...> constraints=<...> holder=<key id> expires=<...>
Call:           tool=<...> args=<normalized map> signer=<key id>
Cause:          caller | policy | configuration | expected denial

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. 19d ago First seen · 90 lines · 111 tokens per session scan A b772a621e015

Subscribe to this mod's changes

tenuo-denial-triage is a skill published in the GitHub repository tenuo-ai/tenuo (103 stars, last pushed today), licensed Apache-2.0. It adds 111 tokens to every session and 2,046 once invoked, about $0.0004 per session on Opus 5.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-27.

DebuggingLLMLangChainSecurityai-agentscapabilitiescryptographylanggraph
Related

Other skills, from other repositories

fix-issue

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to…

yonatangross/orchestkit · 82 tokens

error-analysis

Evals-first error analysis for LLM apps: clusters real Langfuse or JSONL traces into a human-confirmed failure taxonomy with counts, then recommends binary pass/fail evals for recurring named modes. Use to learn what to measure before writing evals. Not for CI failures.

yonatangross/orchestkit · 61 tokens

rust-tracing

Add or change Rust diagnostic tracing in litellm-rust, including route spans, subscriber layers, and Python logger delivery.

BerriAI/litellm · 28 tokens

ci-debug

Diagnose a failing CI run against an 11-pattern playbook. Classifies the failure, cites the relevant memory entry, proposes the exact fix command — but NEVER applies without explicit user approval. Use when a specific PR check or GitHub Actions run failed and you want a diagnosis instead of speculation. Don't use for…

yonatangross/orchestkit · 92 tokens

monitoring-observability

Monitoring and observability patterns for Prometheus metrics, Grafana dashboards, Langfuse v4 LLM tracing (astype, scorecurrentspan, shouldexportspan, LangfuseMedia), and drift detection. Use when adding logging, metrics, distributed tracing, LLM cost tracking, or quality drift monitoring.

yonatangross/orchestkit · 69 tokens

paired-probe

Refuse a verdict a probe did not earn. Runs a check where the fault IS present and where it is NOT, and blocks the answer when both arms print the same thing, because a check that cannot disagree with you has measured nothing. Also catches the zero-sample sweep that reads as "clean" and the swallowed error that reads…

yonatangross/orchestkit · 100 tokens