DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to screen existing drafts for account-risk signals before posting with Yominpost

Run the pre-publish risk gate on drafts you already wrote to catch leaks, bait and duplicates.

Authorization notice. Yominpost is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA social media manager with drafts written elsewhere who wants to avoid signals that get AI-assisted accounts restricted.

The problemDrafts can contain leaked prompt text, engagement bait, hashtag stuffing or duplicates that put the account at risk.

The outcomeA list of risk findings per draft, so you can fix or drop risky posts before they are scheduled.

What you need first

  • uv installed (curl -LsSf https://astral.sh/uv/install.sh | sh)
  • Internet access so uvx can fetch the repo from GitHub
  • A source text, URL or image links to turn into posts
  • Optional: an OAuth app for each platform you want to publish to (see docs/REGISTER_APPS.md)
  • Optional: an API key or a logged-in local claude or codex CLI for better copy; the default template driver needs no key

Steps

  1. Install and start the studio with uvx --from git+https://github.com/mrlong0129/yominpost yominpost --open.
  2. Paste or save each existing draft into the studio so it appears in the post list.
  3. Run the risk gate on each draft; it checks prompt-leak and engagement-bait lint, hashtag and link limits, duplicates and cadence caps.
  4. Edit or delete any draft flagged by the gate.
  5. Schedule only the drafts that pass.

Prompt for your agent

Using the yominpost repo at github.com/mrlong0129/yominpost, run check_post on each draft in <your draft file or list> and report the findings. Expected output: one risk result per draft. Verify that the findings name the rule that fired, such as hashtag limits or duplicate detection.

Caveat. The gate is a set of rules that reduce risk and cannot guarantee that a platform will not restrict an account.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page