Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add PaymobAccept/Paymob-AI-Integration-Skill/plugin install paymob-integrationWrote 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/commands/paymobaccept/paymob-ai-integration-skill/paymob-check-hmac)<a href="https://agentmods.dev/commands/paymobaccept/paymob-ai-integration-skill/paymob-check-hmac"><img src="https://agentmods.dev/badge/commands/paymobaccept/paymob-ai-integration-skill/paymob-check-hmac/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/commands/paymobaccept/paymob-ai-integration-skill/paymob-check-hmac"><img src="https://agentmods.dev/badge/commands/paymobaccept/paymob-ai-integration-skill/paymob-check-hmac.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.00016 | $0.01165 |
| Opus 5 | $0.00008 | $0.00583 |
| Sonnet 5 | $0.00003 | $0.00233 |
| Haiku 4.5 | $0.00002 | $0.00117 |
Grade A, and why
paymob-check-hmac 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit the user's Paymob webhook HMAC verification code: $ARGUMENTS
Non-negotiable ground rules for this command, before anything else:
- Never ask the user to paste their HMAC secret, API key, or Secret Key into this conversation.
- Never read a
.envfile's actual secret value, and never echo, print, or write any secret into chat output, logs, or a file you create. - The default mode is a static code audit — no computation is required to complete it.
- Never audit the field order, digest, or callback shape from memory. This command deliberately carries no copy of the spec. If you cannot read
hmac-verification.md, you cannot do this audit — say so and stop. An audit performed from recall can pass a wrong field order as correct, which is the exact failure this command exists to catch: HMAC verification that looks verified and silently is not.
Step 0 — locate the spec
hmac-verification.md lives in the skill's references/ directory. Use the first of these that exists:
${CLAUDE_PLUGIN_ROOT}/skills/paymob-integration/references/— plugin install~/.claude/skills/paymob-integration/references/— personal skill install.~is the user's home directory; on Windows expand it yourself (%USERPROFILE%\.claude\skills\…), since a literal~will not resolve there.skills/paymob-integration/references/— repository checkout, relative to the working directory. This only resolves if the user happens to be working inside the skill repo, so treat path 2 as the reliable one for a personal install.
${CLAUDE_PLUGIN_ROOT} is substituted only for plugin installs. If you see it unexpanded, you are not in one — use path 2 or 3. If none resolve, search for hmac-verification.md under any paymob-integration directory. Confirm you have actually read the file before starting Step 2.
Step 1 — locate the code
If $ARGUMENTS names a path, start there. Otherwise search for the callback route bound to notification_url / the hmac query parameter, or for PAYMOB_HMAC_SECRET usage.
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.
- 10d ago First seen · 54 lines · 16 tokens per session scan A 9ba64181e974
paymob-check-hmac is a command published in the GitHub repository PaymobAccept/Paymob-AI-Integration-Skill (30 stars, last pushed 26d ago), licensed MIT. It adds 16 tokens to every session and 1,165 once invoked, about $0.0001 per session on Opus 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-08-30.
Other commands, from other repositories
repository-patch
Generate an AbstractPatch repository patch that migrates existing data or structure between module versions, runs exactly once per repository, and is recorded in alfappliedpatch. In-Process SDK (Maven) only.
content-model
Generate Alfresco content model XML and Spring context file from requirements.
design-api-integration
Design an integration with a third-party API so its failures and changes stay contained.
design-caching
Design a caching layer with explicit invalidation, chosen for a specific access pattern rather than added generally.
api-contract
Write a human-readable API contract companion as Markdown in the user's repository. Use when invoked as /document-design-system:api-contract. Produce designed HTML or PDF only when asked.
checklist
Generate a custom checklist for the current feature based on user requirements.