Borrowing it
Nothing to install: this file belongs to Luligu/matterbridge-hass. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Luligu/matterbridge-hass/main/.agents/skills/verify-agent-context/SKILL.mdgit clone --depth 1 https://github.com/Luligu/matterbridge-hassWrote 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/luligu/matterbridge-hass/verify-agent-context)<a href="https://agentmods.dev/skills/luligu/matterbridge-hass/verify-agent-context"><img src="https://agentmods.dev/badge/skills/luligu/matterbridge-hass/verify-agent-context/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/luligu/matterbridge-hass/verify-agent-context"><img src="https://agentmods.dev/badge/skills/luligu/matterbridge-hass/verify-agent-context.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.00475 |
| Opus 5.5 | $0.00021 | $0.00190 |
| Sonnet 5.5 | $0.00011 | $0.00095 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
verify-agent-context 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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- verify-agent-context — 100% identical, 0 lines differ
What it actually says
Agent configuration check
Run this check and reply with a short report. Do not modify any file.
- First, report the absolute current working directory and whether you are working in a linked Git worktree or a direct folder (the main checkout or a non-Git folder). Verify using
git rev-parse --show-toplevel,git rev-parse --absolute-git-dirandgit rev-parse --path-format=absolute --git-common-dir: different Git and common directories indicate a linked worktree; matching directories indicate the main checkout. If the folder is not a Git repository, report it as a direct non-Git folder. Report the current branch usinggit symbolic-ref --quiet --short HEAD; if HEAD is detached, reportdetached HEADand the short commit ID fromgit rev-parse --short HEAD. For a non-Git folder, report the branch as not applicable. Include the repository root when it differs from the current directory, and make this location and branch information the first row of the report. - State which agent you are (GitHub Copilot, Codex, Claude Code or Gemini / Antigravity) and, if known, the model.
- Confirm you have the shared instructions from
AGENTS.mdin context. Quote its title line, including the version. - List the rule files in
.agents/rules/and, for each, say whether its content is already in your context or only reachable on demand. - List the skills you discovered from
.agents/skills/and from any tool-specific folder such as.claude/skills/or.github/skills/. - Read
.agents/rules/testing.instructions.mdand report the version at the end of itsdescriptionfrontmatter to prove the file is readable. - Report the result as a markdown table with the columns
Item,Status,Notes. - Report the context size, including the number of instructions, rules, and skills currently loaded.
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.
- 5d ago First seen · 18 lines · 53 tokens per session scan A 6f4736424f30
verify-agent-context is a skill published in the GitHub repository Luligu/matterbridge-hass (195 stars, last pushed 4d ago), licensed Apache-2.0. It adds 53 tokens to every session and 475 once invoked, about $0.0002 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-10-24.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.