Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

I built a Python script that automatically reads IP addresses from a file, queries a threat intelligence API (AbuseIPDB) Checks each IP’s abuse confidence score Flags suspicious IPs (e.g., known for spam, DDoS, malware)and saves flagged IPs into a blocklist file.

95,880 Aufrufe • vor 1 Jahr •via X (Twitter)

12 Kommentare

Profilbild von Coding Ninja 🥷🏾
Coding Ninja 🥷🏾vor 1 Jahr

@cyber_rekk @donteatme_1 @Cyber_indaboski @ireteeh Github link :

Profilbild von RTTS
RTTSvor 2 Jahren

API testing of interfaces is critical to determine if they meet requirements for functionality, reliability, performance, and security. Check out RTTS - the automated testing experts since 1996. #API #testautomation #integrationtest

Profilbild von VOICE×OF×THE-STREET
VOICE×OF×THE-STREETvor 1 Jahr

Bro, is this obs studio? The screen recorder?? And great Job, check my TL for some python project I can try.

Profilbild von Coding Ninja 🥷🏾
Coding Ninja 🥷🏾vor 1 Jahr

Nahh I just used the snipping tool on windows 11, it has a screen recording feature now Thank you bro, I would definitely check your page for ideas man

Profilbild von CYB3R - H4CK3RTR0N
CYB3R - H4CK3RTR0Nvor 1 Jahr

Great job bro

Profilbild von Coding Ninja 🥷🏾
Coding Ninja 🥷🏾vor 1 Jahr

Thank you bro

Profilbild von Chinyere | Cybersecurity ✍️
Chinyere | Cybersecurity ✍️vor 1 Jahr

This is incredible 👏👏👏

Profilbild von Coding Ninja 🥷🏾
Coding Ninja 🥷🏾vor 1 Jahr

Thank you broo

Profilbild von Cyber indaboski
Cyber indaboskivor 1 Jahr

Nice work bro 👏

Profilbild von Coding Ninja 🥷🏾
Coding Ninja 🥷🏾vor 1 Jahr

Thank youuu broo

Profilbild von Olúmáyòwá.dev
Olúmáyòwá.devvor 1 Jahr

This is lovely !!

Profilbild von Coding Ninja 🥷🏾
Coding Ninja 🥷🏾vor 1 Jahr

Thank you sir!

Ähnliche Videos

Here's how I'm running automated content engine in 2 files 1 markdown file = my wiki 1 html file = my dashboard that's the whole stack. [ the architecture, in plain words ]: LLM wiki = a single markdown file holding my audience DNA, 15 tracked creators, every viral topic from the last 30 days HTML artifact = a single page that reads that markdown file AND can trigger my agents the artifact and the agent talk to each other directly the wiki is the shared brain [ what I actually see when I open it at 9am ]: > 5 trending topics ranked by my audience-DNA fit > 3 KOL posts worth quoting today > last week's saved tweets (so I can ride waves that are still warm) > buttons: [draft tweet] [draft QT] [schedule] [log idea] 1. I click "draft tweet" on a topic 2. the artifact pings my agent 3. agent reads the wiki, drafts in MY voice, returns it to the artifact 4. I edit, schedule, done 15 minutes from morning coffee to 3 scheduled posts [ how to build the same in one evening ]: > step 1: dump your domain knowledge into ONE markdown file (audience profile, KOL list, content rules, voice guide, anything an agent would need to do YOUR job) > step 2: ask claude to build an html artifact that reads from that file ("here's my wiki, build me a dashboard with these views") > step 3: add buttons for the actions you do daily (draft, schedule, log, score, search — your workflow, not mine) > step 4: wire each button to call your agent via tool calls (so the artifact and the agent talk directly) the moment your artifact reads your wiki AND triggers your agents.. most SaaS tools you currently pay for quietly become unnecessary dashboards I used to pay $50/month for now sit in a single html file I can rebuild in 20 minutes every "I'll build a SaaS for this" idea you had last year is a 200-line file you write in an afternoon if you want to get the same content engine, just reply "CONTENT" and will send you in DMs later we're going from buying software to owning it.

Ronin

50,083 Aufrufe • vor 3 Monaten

HERMES AGENT RUNS MONITORING, RESEARCH, LEAD DETECTION, AND COMPETITIVE ANALYSIS ON AUTOPILOT. AND KNOWS WHEN NOT TO SPEND YOUR TOKENS. the biggest unlock most people skip: Hermes cron jobs can decide ON THEIR OWN whether the LLM should wake up. WAKE AGENT — THE $0 GATE every cron job can run a Python script first. the script checks: did anything actually change? nothing changed: → script outputs {"wakeAgent": false} → LLM stays asleep → zero tokens spent something changed: → script outputs {"wakeAgent": true} → agent wakes up and handles it three gate patterns from official docs: → file-change: compare file mtime to last run. no change? sleep. → external-flag: another process drops a ready file. no flag? sleep. → HTTP-check: ping a URL, diff the response. same as last time? sleep. real example: monitor AWS costs every hour. script pulls current spend from AWS API. no spike? agent sleeps. zero cost. costs jump 40%? agent wakes, reports to Slack, takes action through Stripe MCP. you run 20 monitoring jobs a day. 18 of them find nothing. you pay for 2. NO AGENT — PURE SCRIPT, ZERO LLM some jobs don't need reasoning at all. TLS checks. uptime pings. disk alerts. heartbeats. hermes cron edit --no-agent --script check_health.py script runs. stdout goes straight to Telegram, Discord, or Slack. no LLM involved. flip any job between modes: hermes cron edit --agent # add LLM hermes cron edit --no-agent # remove LLM free monitoring that lives inside the same ecosystem as your agent. 4 MORE USE CASES THIS UNLOCKS: COMPETITIVE ANALYSIS weekly cron with script that diffs competitor pages. agent only analyzes actual changes. updates your tracking file and PRD skill automatically. PRD AS A SKILL save product requirements as a skill, not a document. skills load on demand into fresh context. documents drift. skills stay sharp. CONTENT REPURPOSING hand a video script to the agent. it drafts X and LinkedIn posts in your voice. writes to a review folder. you approve via Telegram. LEAD DETECTION webhook monitors inbox. agent spots potential leads. drafts responses using your business context. schedules meetings from your calendar. the pattern across all of these: scripts handle the mechanical work for free. the agent only spends tokens on reasoning that requires judgment. comment CRON and I'll send you 5 ready-to-paste cron configs with wakeAgent and no_agent patterns. full Hermes SOUL.MD guide 👇

YanXbt

95,883 Aufrufe • vor 1 Monat

I used Grok 4.5 through Hermes to automatically generate ~80% of the video below. This is part of a series for Paid Subscribers on X and Exclusive Members on YouTube called Musk Industry Daily. It autonomously does the following: It finds the latest, most important news happening in the Musk Ecosystem from the last 24 hours. Analyzes them against a knowledge repository that was cultivated from the corpus of my 1800+ videos, my 2 books, and my articles on X. It writes a script that explains what's happening, why it's important, what people are saying about it, what the risks are, and what my specific take is. It fact checks & sources the entire script and corrects any errors, plus improves any stylistic choices. It generates slides that are used as b roll material for the video. It runs it through the clone of my voice on ElevenLabs. It packages all the materials up into a Google Drive, including the script, sourcing, cue cards for editors to know when to insert materials, the voice file, and a few other reference materials. It runs daily at 12:30AM CT. The editors then take all the materials, quickly package them together into the video, and upload it to my YouTube channel for exclusive members only. Then an autonomous Hermes agent running Grok 4.5 will pick that file up, cross-post it to X for subscribers only, including a written summary of each item in the replies. -- If you find this valuable, consider becoming a subscriber!

Farzad 🇺🇸 🇮🇷

14,875 Aufrufe • vor 1 Monat

I just built a Brand Operating System inside Claude Cowork 🤯 A connected system of files that every skill automatically reads from, so your hook writer, brief generator, and script writer all speak in your exact brand voice. All inside Claude Cowork. Perfect for DTC brands and agencies tired of generic AI output that sounds like every other brand in their category. If you're opening a new Claude chat and re-explaining your brand, re-pasting your voice guidelines, and re-describing your customers every single time, a Brand OS fixes the entire loop: → Build 3 foundation files once per brand → Every skill you create reads from the Brand OS automatically → Hook writer pulls your voice + customer pain points → Brief generator pulls your positioning + angles → Script writer pulls the brief + brand DNA → Every output is calibrated to your brand on the first pass No re-briefing Claude on every chat. No editing for an hour to fix generic AI phrasing. No creative that sounds like it could belong to any brand. What you get in the playbook: → The exact Brand OS file structure I use → Templates for all 3 files you can fill in for any brand → The architecture that makes every Claude skill 10x sharper → The exact setup for agencies running a Brand OS per client For agencies: this is how you build a perfect, reusable knowledge base for every client on your roster. Set up the Brand OS once per client, and every campaign after that is already calibrated. I put together a full playbook with the file templates, the architecture, and the exact setup process so you can build your own Brand OS for your brand or your clients. Want it for free? > Like this post > Comment "OS" And I'll send it over (must be following so I can DM)

Mike Futia

30,214 Aufrufe • vor 4 Monaten

I just built a Claude skill that acts as a second brain for DTC brands 🤯 Drop your ad exports, customer reviews, competitor screenshots, and brand docs into a folder → Claude compiles it all into an organized wiki you can ask questions against. All inside Claude Cowork. Perfect for DTC brands and agencies whose knowledge is scattered across Google Drive, Notion, Meta Ads Manager, Figma, and 47 spreadsheets nobody has opened in 3 months. If every strategic question takes 2 hours to answer because the data lives in 8 different places ... This skill eliminates the entire loop: → Claude scaffolds a DTC folder structure: ads, customers, competitors, brand, performance, notes → You drop every file you have into those folders — messy, unorganized, exactly how you have them now → Claude reads everything and compiles a wiki: hooks-that-work, customer-pains, competitor-angles, brand-voice, performance-patterns, creative-brief-library → Every article is cross-linked and traceable back to the source file → You ask questions against the wiki — "what hooks are actually working?" "what objections come up most?" "where are my competitors weak?" → Claude answers, grounded entirely in your own data → Save the answers back in and the system gets smarter every time you use it No more hunting through 12 tools. No more "where did I save that brief?" No more answering the same question twice. What you get: → A complete DTC brand brain scaffold in 60 seconds → Six core wiki articles Claude populates automatically from your raw files → A schema file that tells Claude exactly how to maintain the wiki for DTC use cases → Monthly health checks that catch contradictions and flag gaps before errors compound → A knowledge base that compounds — every question you ask makes the next answer better Built on a methodology Andrej Karpathy shared for personal knowledge bases, I rebuilt the entire thing for DTC operators: folder structure, schema rules, wiki articles, and question frameworks all tuned for brands and agencies. I put together the full skill file plus a playbook walking through the exact setup and 5 real questions to ask your brand brain. Want it for free? > Like this post > Comment "BRAIN" And I'll send it over (must be following so I can DM)

Mike Futia

15,210 Aufrufe • vor 4 Monaten