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 Glad-Labs/poindexter --skill reject-postgit clone --depth 1 https://github.com/Glad-Labs/poindexterWrote 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/glad-labs/poindexter/reject-post)<a href="https://agentmods.dev/skills/glad-labs/poindexter/reject-post"><img src="https://agentmods.dev/badge/skills/glad-labs/poindexter/reject-post/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/glad-labs/poindexter/reject-post"><img src="https://agentmods.dev/badge/skills/glad-labs/poindexter/reject-post.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.00044 | $0.00220 |
| Opus 5 | $0.00022 | $0.00110 |
| Sonnet 5 | $0.00009 | $0.00044 |
| Haiku 4.5 | $0.00004 | $0.00022 |
Grade A, and why
reject-post 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.
What it actually says
Reject Post
Rejects a content task, marking it for revision or removal from the pipeline.
Usage
scripts/run.sh "task_id" "reason" [feedback]
Parameters
- task_id (string, required): The ID of the task to reject. Accepts a full UUID, a numeric legacy ID, or a short UUID prefix of 6 or more characters.
- reason (string, required): Explanation for the rejection, captured on the task record.
- feedback (string, optional): Detailed reviewer feedback for the revision. Defaults to the reason when omitted.
- allow_revisions (boolean, optional): Whether the task may be sent back for revision. Defaults to
true(server-side).
Output
Returns the updated task object confirming the rejection.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 26 lines · 44 tokens per session scan A aea04c58da90
reject-post is a skill published in the GitHub repository Glad-Labs/poindexter (5 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 220 once invoked, about $0.0002 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
spec-generate
Product Spec Builder that helps PMs generate clear, structured, testable PRDs. Creates both full and lightweight specs for any product or platform with a guided step-by-step workflow. Output in English Markdown format.
product-team
A Chinese-language product development workflow led by one AI team lead taking several roles: product strategy, requirements writing, prototype creation, and user-experience review.
Playwright (Automation + MCP + Scraper)
Browser automation via Playwright MCP. Navigate websites, click elements, fill forms, take screenshots, extract data, and debug real browser workflows. Use when (1) you need a real browser, not static fetch; (2) the task involves Playwright MCP, browser tools, Playwright tests, scripts, or JS-rendered pages; (3) the…
ux-walkthrough-skill
A user-experience review process that examines a product’s screens and user journeys against its product requirements document (PRD). It checks consistency, accessibility, errors, and whether users can complete tasks clearly.
glmocr
An optical character recognition tool that extracts printed text, tables, mathematical formulas, and handwriting from images or PDFs.
guide
A project-guide workflow that summarizes the OpenClaw Bot system, its commands, enabled skills, memory, and recent social publishing activity.