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.
npx skills add seranking-planable/smm-skills --skill pending-approvals-roundupgit clone --depth 1 https://github.com/seranking-planable/smm-skillsWrote 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/seranking-planable/smm-skills/pending-approvals-roundup)<a href="https://agentmods.dev/skills/seranking-planable/smm-skills/pending-approvals-roundup"><img src="https://agentmods.dev/badge/skills/seranking-planable/smm-skills/pending-approvals-roundup/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/seranking-planable/smm-skills/pending-approvals-roundup"><img src="https://agentmods.dev/badge/skills/seranking-planable/smm-skills/pending-approvals-roundup.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.00110 | $0.00819 |
| Opus 5 | $0.00055 | $0.00409 |
| Sonnet 5 | $0.00022 | $0.00164 |
| Haiku 4.5 | $0.00011 | $0.00082 |
Grade A, and why
pending-approvals-roundup 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 11d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pending approvals roundup
Surface all posts waiting for approval across one or more Planable workspaces, so nothing gets missed.
How this skill works
- Identify which workspaces to check
- Fetch posts filtered by approval status
- Summarize clearly — grouped by workspace/client, with post previews and context
Step 1: Scope the check
Ask (or infer from context):
- Which workspaces? — a specific client, a list, or all workspaces
- Whose approvals? — posts pending the user's own approval (
PENDING_MY_APPROVAL) or all pending posts (NOT_APPROVED,PARTIAL_APPROVED)
Default behavior if not specified: fetch PENDING_MY_APPROVAL across all workspaces (or the most recently active ones if there are many).
Step 2: Fetch pending posts
For each workspace in scope:
list_posts(
workspaceId,
approvalStatus: ["PENDING_MY_APPROVAL"] // or NOT_APPROVED, PARTIAL_APPROVED
)
Approval status reference:
| Status | Meaning |
|---|---|
PENDING_MY_APPROVAL |
Posts where this user is a required approver |
NOT_APPROVED |
Posts with no approvals yet |
PARTIAL_APPROVED |
Posts with some but not all required approvals |
REQUESTED_BY_ME |
Posts where this user requested approval from others |
If the user wants a broader view, query NOT_APPROVED and PARTIAL_APPROVED together.
Step 3: Organize and present results
If results exist, group by workspace (client). For each post show:
- Platform/page name
- Post preview (first 100–150 chars of
textPreview) - Scheduled date (if set) — flag posts that are scheduled soon (within 24–48 hours)
- Current approval status
- Number of approvals received vs. required (if available)
Sort order within each workspace: most urgently scheduled first, then by creation date.
Format:
📋 [Workspace name]
• [Platform] — "[Post preview...]"
Scheduled: [date] ⚠️ (if within 48h)
Status: [approval status]
• [Platform] — "[Post preview...]"
No date set
Status: Partially approved (1/2)
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.
- 11d ago First seen · 102 lines · 110 tokens per session scan A 22243a6d906a
pending-approvals-roundup is a skill published in the GitHub repository seranking-planable/smm-skills (3 stars, last pushed 2mo ago), licensed MIT. It adds 110 tokens to every session and 819 once invoked, about $0.0006 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-31.
Other skills, from other repositories
analytics-strategy
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement.…
content-strategy
Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align…
incident-response
Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers…
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
agb-begriff-vorformuliert-305
Für AGB Begriff Vorformuliert 305: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: agb-begriff-vorformuliert-305.
blue-pencil-board-agb-bonitaetspruefung-bonus
Für Blue Pencil und Geltungserhaltende Reduktion: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Tatbestands- oder Anspruchsmatrix.