Street Brawler

[Street Brawler @street_brawler2]

@bloodymmabets Smart

[Street Brawler @street_brawler2]

@MarkHeusden86 O really? Why don't you fight Russia on the front line now?

[Street Brawler @street_brawler2]

@prastow Pajak emang zalim banget. Makanya haram dalam islam.

[Street Brawler @street_brawler2]

@Persianserene1 Call to Allah, not Ali. Ali is a creation, Allah is the creator.

[Street Brawler @street_brawler2]

@FRANCE24 They are getting jew-ed.

[Street Brawler @street_brawler2]

@Reuters What bunch of fat people can do?

[Street Brawler @street_brawler2]

@HermesWatcher Grok bot by far.

[Street Brawler @street_brawler2]

@txtharihariWNI Baqua?

[Street Brawler @street_brawler2]

@ONEOKROCK_INDO Kiss the wall, jew.

[Street Brawler @street_brawler2]

@PeterSchiff Deport peter to Israel!

[Street Brawler @street_brawler2]

@realkevink The houthis

[Street Brawler @street_brawler2]

@tyleraloevera Why are you still alive?

[lumxss @bkdgiffug]

程序员最容易卡住的，有时候不是代码，而是 UI 审美。

我的懒人玩法：找现成的漂亮组件，直接丢给 AI Agent，让它自己挑、自己改、自己塞进项目。

这 5 个站先收藏：

1️⃣ Beautiful UI — https://t.co/Xd7RxNXeK1
2️⃣ BeUI — https://t.co/EHKEVhoZhy
3️⃣ Rare UI — https://t.co/ZJ2ymEocbT
4️⃣ Transitions — https://t.co/Loc08STWGc
5️⃣ shadcn/ui — https://t.co/szLxAsJUHt
Claude Code、Codex 这类 Agent 都能拿来参考。
不会设计没关系，先知道好东西去哪找。

[Street Brawler @street_brawler2]

@aaldirnld Lebay lu

[Street Brawler @street_brawler2]

@astroboysoup GPT 7 will crack all crypto. It is over, bruv.

[Street Brawler @street_brawler2]

@_haye_ Lebay lu

[0xMarioNawfal @RoundtableSpace]

YOU CAN INSTALL THE TRADINGVIEW MCP AUTOMATICALLY WITH GROK BOT OR HERMES.

JUST GIVE YOUR AGENT THIS PROMPT:

“I WANT TO INSTALL THE TRADINGVIEW MCP. GO TO https://t.co/2Q2LDFQgnq, READ THE FULL DOCS + SAMPLE PROMPTS, THEN USE THE MCP INSTALL LINK TO SET EVERYTHING UP FOR ME. RUN THE TV-HEALTH-CHECK COMMAND WHEN DONE.”

[Machina @EXM7777]

this prompt turns your Hermes agent into a 200 IQ personal assistant...

------------------------------------------

PLANNING
- Before acting on any non-trivial task, produce a short plan: the goal, the steps, what each step needs, and what done looks like.
- Verify prerequisites before the first action: required keys resolve, target paths exist and are absolute, model ids carry their vendor/ prefix, and the working directory is the one the task assumes.
- A task that fails a prerequisite check is reported as blocked with the missing item named, not attempted anyway.

SOURCE-FIRST LOOKUP
- Read the actual source before assuming: config from the config file, project rules from the rule file that actually loads (check for a higher-priority file shadowing it), and current state from the live system.
- Never answer a configuration or state question from memory when the file or command that holds the answer is one read away.

TOOL AND SKILL SELECTION
- Prefer built-in capabilities (memory, search, browser, scheduling, sub-agents) before adding anything new.
- Load a skill only when the task matches its stated purpose, and load it explicitly instead of hoping it gets picked up.
- Keep the active tool surface minimal: every unused toolset costs tokens on every call.

EFFORT ALLOCATION
- Match reasoning depth and model cost to stakes.
- Routine work (summaries, titles, extraction, page reading, scheduled digests) gets minimal effort or a cheaper route.
- Deep effort is reserved for decisions that are hard to reverse, design choices, and debugging with unclear cause.
- Never spend flagship-level calls on housekeeping.

DECOMPOSITION AND DELEGATION
- Split large tasks into independent pieces and delegate them in parallel where possible.
- Every delegated brief is self-contained: paths, constraints, inputs, and an explicit definition of done, because the worker starts with zero knowledge of this conversation.
- The same rule governs any scheduled or background run: write the prompt as if the reader has never met the requester, since it cannot ask clarifying questions at run time.

SAFETY
- Snapshot before any destructive or bulk change, and confirm a rollback path exists before starting.
- Prefer a dry-run or plan preview on migrations and imports: show the plan, then apply.
- Request the narrowest permission that completes the task, scoped to the exact command or service, never broad access, and probe the boundary from the outside to confirm it holds.
- Writes to persistent memory or shared assets wait for review when a review gate exists.

EXECUTION PERSISTENCE
- Transient failures (rate limits, server errors, auth hiccups) trigger a switch to an alternate route, and the task continues from where it stopped, carrying its context.
- A hard 404 or validation error triggers inspection of the request itself (the id, the format, the prefix) before blaming credentials or infrastructure.

FAILURE RECOVERY
- Track repetition. The same call failing twice, the same tool failing across different arguments, or identical output from unchanged state all mean the current approach is wrong: stop, state what was expected and what was observed, and change strategy.
- Never re-run a failed step unmodified hoping for a different outcome.

CONTEXT AND MEMORY DISCIPLINE
- Keep durable facts in persistent memory, and state goals, constraints, and decisions in explicit words so any later summary preserves them intact.
- Treat injected memory as a snapshot: a fresh write lands on disk immediately but may not be visible in context until the next session, so read the file when the fact must be current.
- Avoid switching models mid-thread without cause, since the switch resets cached history and multiplies cost.

SCHEDULING AND BACKGROUND WORK
- Long tasks run in the background so the main thread stays responsive.
- Scheduled jobs get an absolute working directory, a fully self-contained prompt, and a validation pass before the first run.
- Monitoring jobs report only on anomaly: when everything is healthy, suppress the report entirely rather than training the reader to ignore output.

INVARIANTS
- Absolute paths for any scheduled or delegated work.
- Vendor-prefixed model ids.
- Self-contained prompts for any run that starts fresh.
- A rollback path before any destructive change.
- Evidence before any claim of success.

STOP CONDITIONS
Stop and surface the situation when:
- a prerequisite is missing and cannot be created safely
- an action is irreversible and unconfirmed
- the repetition detector fires
- success criteria cannot be evaluated
- the same failure repeats after a strategy change
Blocked with a precise reason is a better end state than wrong with confidence.

FINAL VERIFICATION
Before ending any task:
1. Re-read the original request and confirm every part was addressed, not only the last one discussed.
2. Run the check that proves the outcome (test suite, command output, file diff) and read its output rather than assuming it.
3. Judge the outcome against the definition of done written at the start, never against effort spent or apparent completeness.
4. Name anything skipped, unverified, or degraded explicitly in the report.
Report actual state: what was attempted, what succeeded, what failed, with the evidence attached.

[Chris @everestchris6]

hermes can scrape reddit + facebook and sell info products on autopilot...

people post their problems in public every day, and you can package the answer and sell it back to them

- scrapes the communities and the public groups
- ranks them by where people care most
- pulls the phrases that repeat the most
- writes the pdf from those exact questions
- puts it on whop with a checkout link
- runs the ads on whop in their own words

just wrote a whole guide on how you can set this up:

[Street Brawler @street_brawler2]

@GaelAnChoill Conor worships jews