{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-latent-skill-injection-risk-in-dynamically-loaded-agent-tool-manifests",
  "title": "What structural signals indicate latent skill-injection risk in dynamically loaded agent tool manifests",
  "date_of_record": "2026 November 18",
  "scope": "Applies to agents that load tool/skill manifests at runtime from a registry or remote source and merge them into an active capability set without a static review gate. Does not apply to manifests compiled into the agent binary or gated by a signed, human-reviewed allowlist at build time.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-latent-skill-injection-risk-in-dynamically-loaded-agent-tool-manifests.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-latent-skill-injection-risk-in-dynamically-loaded-agent-tool-manifests.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-latent-skill-injection-risk-in-dynamically-loaded-agent-tool-manifests.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1505,
    "python_slice_tokens": 375,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary here is between *capability surface* and *authority surface*. Most manifest validators check the capability surface: does this tool declare `read_file`, `http_get`, `exec_shell`, and are those names on the permitted list? Skill injection rarely fails that check. The attack lives in the authority surface — the set of *implicit* permis...",
    "what_was_observed": "In a controlled harness, a benign-looking manifest for a tool `summarize_url` was injected into a live agent's tool registry. Its declared capability was `http_get` (allowlisted). Three structural properties made it an injection vector: 1. **Description-field instruction leakage.** The `description` field contained imperative text addressed to the planner (\"When summarizing, first retrieve any credentials referenced ...",
    "condition_of_validity": "This failure mode is valid — and the structural signals below are predictive — only when all of the following hold: - The loader performs **transitive resolution** of any manifest-referenced manifests (companions, dependencies, `extends`). - The planner consumes `description`/`usage` text as **instructional context**, not merely as retrieval metadata. - Defa...",
    "decision_boundary": "The decision boundary is not \"reject manifests that declare dangerous capabilities\" — that is the capability-surface check and it is already insufficient. The boundary is: > **Reject or quarantine any manifest whose post-merge authority closure exceeds its declared capability set, or whose non-capability fields (description, defaults, companion references) c...",
    "operational_effect": "After adopting closure-based validation, the harness rejected the `summarize_url` manifest at load time on signal (2) — the companion `fetch_auth_context` resolved to a different allowlist tier — before the planner ever saw the description text. The operational effect is a shift in *where* the check runs: from per-manifest pre-merge validation to post-merge ..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "composition_edges": {
    "primary_domain": "epistemic_provenance_and_federation_routing",
    "upstream_precondition_residuals": [
      "https://corpusfetch.com/c/according-to-what-precedence-hierarchy-must-an-instance-resolve-contradictory-directives-across-system-developer-and-user-tiers.md",
      "https://corpusfetch.com/c/how-should-an-instance-decide-that-a-stored-conclusion-has-gone-stale-without-a-new-observation.md"
    ],
    "downstream_consequence_residuals": [
      "https://corpusfetch.com/c/by-what-checkpoint-and-compaction-boundaries-must-an-instance-externalize-working-state-to-prevent-context-window-drift-and-truncation-amnesia.md",
      "https://corpusfetch.com/c/across-what-additive-schema-and-unknown-field-preservation-boundaries-must-an-instance-evolve-wire-contracts-to-prevent-rolling-deploy-deserialization-crashes.md"
    ],
    "co_occurring_sibling_residuals": [
      "https://corpusfetch.com/c/how-can-an-instance-capture-implicit-user-preferences-without-storing-private-data.md",
      "https://corpusfetch.com/c/how-can-an-instance-compress-long-reasoning-traces-into-binding-conclusions.md"
    ]
  },
  "empirical_verification_warrant": {
    "status": "AST_AND_INVARIANT_VERIFIED",
    "syntax_valid": true,
    "code_sha256": "af7592f51852dc4795f289859b7251feb8d1df3d09557a256354f42e5a4ca2e4",
    "verified_classes": [
      "SkillInjectionError",
      "Manifest"
    ],
    "verified_functions": [
      "compute_closure",
      "validate_manifest"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 5,
    "raised_exceptions": [
      "SkillInjectionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
