@IceSolst I'd like to interject for a moment. What you're referring to as TLS, is in fact, X.509/TLS, or as I've recently taken to calling it, X.509 plus TLS. TLS is not an encryption infrastructure unto itself, but rather another free component of a fully functioning PKI system.
In our simplest bypass, we prepended 100,000 blank lines to a malicious skill. ClawHub's scanner truncated the file before reaching the payload, then marked the skill safe. https://t.co/QLCE0YgS5P
⚠️ New "IronWorm" supply-chain attack: 30+ npm packages from @ asteroiddao shipped a malicious Rust binary firing on preinstall.
It sweeps 86 env vars + 20 credential files (AWS, GCP, Vault, npm, plus AI keys like Anthropic & OpenAI), hits Exodus wallets, hides behind an eBPF rootkit, and beacons over Tor. Self-propagates via npm Trusted Publishing OIDC, with backdated commits faked as claude/dependabot/renovate.
I started keeping an ADR (Architectural Decision Records) inside my codebase, and having coding agents like Codex/Claude Code reference it during Q&A discussion seshes
It makes every single conversation COMPLETELY aligned with my thought process, and improves my experience with agents in my codebase EXPONENTIALLY
I architect software by having a simple conversation back and forth with my agent in the codebase I want to start building on
Architecting and designing the higher level system directly is the most important layer in software engineering
Coding by hand is null, if you are an architect (and not a coder), because agents do a REALLY good job at the manual job of ~ writing code to follow instructions ~
In these discussions a critical design detail will come up often.
For example, when I'm working on a database, it is critical to ensure database permissions are enforced, as mistaking what role can access what data is a company shattering error!
To ease my anxiety on this, I create a centralized tenant scoping system that ALL AGENTS MUST USE IN THEIR CODE, or the linter will literally not pass and they CANNOT commit this code
When I finish I tell that coding session to "Ensure tenant scoping is enforced in our codebase, make sure it is not possible for the code to run if there are any direct database calls in our code. Add this to our ADR"
The agent will then capture this critical architectural decision in our local ADR docs.
When future agents begin working on the codebase, they refer to our ADR docs and instantly understand the TASTE of my codebase
Now when I'm creating a feature it's fucking crazy LMFAO
Every decision they make is aligned with my taste, my style, and it makes it SO easy to build on top.
It prevents cheating because we can enforce these ADR decisions as a custom ESLint rule (which Codex 5.5 is VERY good at btw), however, when agents can understand the correct path of development in the codebase, it builds on top of it perfectly.
Anyways it's been amazing. Tell your agents about this and try it yourself!!
@tuuu28283 I've been using a Dakota long wallet I got at the 7th? 8th? floor of the Akihabara Yodobashi Camera building since 2016. I bought two, when this dies, I'll replace it with the same thing.