Feed
Pro
Search

Sign in
Darkshift - a dark factory for software Bug0 - The AI-native e2e QA regression testing The foreword by Hashnode - official blog from the Hashnode team Passmark - The open-source AI framework for regression testing Hashnode gql skill - let your AI agent publish to your Hashnode blog Hackathons Changelog Brand @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap

Search Hashnode

Search posts, tags, users, and pages

FeedDiscussion

Kola

Sep 10

I built a security-audit skill for my AI coding setup. It missed a real vulnerability twice.

I've been building a rehearsal environment for OpenCode + Claude — the idea being that before I trust this setup with real work, I put it through deliberate failure tests. One piece of that setup is a

kolaa.hashnode.dev5 min read

Responses(4)

Fawas Kareem

Node.js Backend developer, Flutter mobile developer

Sep 10

This is nice I was recently setting up some my laptop so my coding agents can be more intelligent by adding skills and tools available globally such that any coding agent can refer to it. I should a security skill to it as well

Good read chief 👏

Kola

Sep 11

Thank you for the feedback! Definitely add the security skill, and making it globally available to your coding agents sounds like a solid setup. Just make sure to test it properly too.

Ridwan Kareem

Programmer

Sep 10

This is such a good read, and it also reiterate on how important testing is and not a process that's supposed to be skipped

Kola

Sep 10

Absolutely. That was one of the biggest lessons for me from this. It’s easy to stop testing once things appear to be working, but this reminded me why you really have to test properly and not just assume you’ve covered everything. Thanks for reading!