The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu
Go agent-ai-cliagent-harnessesagent-securitybrowser-extensionciclaude-codecloudcodexcursordetection-engineeringjevknowledge-basememorymobile-device-managementobservabilitysecuritysecurity-information-and-event-managementsecurity-toolstelemetrytraces
fix(agent-skills): sync the embedded beacon-lens-create skill with the published copy
Claude76a4c24e8ca6
diff --git a/cli/beacon/internal/agentskills/skills/beacon-lens-create/SKILL.md b/cli/beacon/internal/agentskills/skills/beacon-lens-create/SKILL.mdindex 7d2fe929..4ddd0678 100644--- a/cli/beacon/internal/agentskills/skills/beacon-lens-create/SKILL.md+++ b/cli/beacon/internal/agentskills/skills/beacon-lens-create/SKILL.md@@ -114,7 +114,8 @@ Things that are easy to get wrong:- **Do not sum `usage` across events for a total.** Some runtimes report the same tokens on twochannels or as cumulative counters. `token_usage.totals` is the deduplicated count; if youalso show per-event figures, say they can add up to more. `cost_usd` is only ever what the- runtime reported; Beacon never estimates cost, and neither should a lens.+ runtime reported. Lens data carries no estimate (Beacon's list-price estimates live in+ `beacon token-usage` and the Tokens page), and a lens must not compute one.- **`fidelity: "inferred"`** marks an action Beacon derived rather than observed (for example anapproval built from a pre-tool notification). Show the difference when it matters.- **Pair calls with results on `tool_call_id`**, not on adjacency, and order by `number` or